Imdad.qa Site Title

IIS Windows Server

Imdad.qa Test Results

Imdad.qa Mobile Performance: 26/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Avoid multiple page redirects. Potential savings of 4,230 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused JavaScript. Potential savings of 228 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 880 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Preload key requests. Potential savings of 180 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
12 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
4.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
3.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
21 requests • 444 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Imdad.qa Mobile SEO: 64/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Tap targets are not sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more. Tap targets are too small because there's no viewport meta tag optimized for mobile screens
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found

Imdad.qa Mobile Best Practices: 64/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Does not use HTTPS
21 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Imdad.qa Mobile Progressive Web App: 25/100
Quick overview:
Fast and reliable
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Does not use HTTPS
21 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
PWA Optimized
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 980px does not match the window size of 360px.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not provide fallback content when JavaScript is not available
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more. The page body should render some content if its scripts are not available.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Imdad.qa Mobile Accessibility: 91/100
Quick overview:
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Similar tests
www.imdad.com
www.imdad.net
www.imdad.org
www.imdad.info
www.imdad.biz
www.imdad.us
www.imdad.mobi
www.mdad.qa
www.imdad.qa
www.umdad.qa
www.iumdad.qa
www.uimdad.qa
www.jmdad.qa
www.ijmdad.qa
www.jimdad.qa
www.kmdad.qa
www.ikmdad.qa
www.kimdad.qa
www.omdad.qa
www.iomdad.qa
www.oimdad.qa
www.idad.qa
www.indad.qa
www.imndad.qa
www.inmdad.qa
www.ijdad.qa
www.imjdad.qa
www.ikdad.qa
www.imkdad.qa
www.imad.qa
www.imxad.qa
www.imdxad.qa
www.imxdad.qa
www.imsad.qa
www.imdsad.qa
www.imsdad.qa
www.imead.qa
www.imdead.qa
www.imedad.qa
www.imrad.qa
www.imdrad.qa
www.imrdad.qa
www.imfad.qa
www.imdfad.qa
www.imfdad.qa
www.imcad.qa
www.imdcad.qa
www.imcdad.qa
www.imdd.qa
www.imdqd.qa
www.imdaqd.qa
www.imdqad.qa
www.imdwd.qa
www.imdawd.qa
www.imdwad.qa
www.imdsd.qa
www.imdasd.qa
www.imdzd.qa
www.imdazd.qa
www.imdzad.qa
www.imda.qa
www.imdax.qa
www.imdadx.qa
www.imdaxd.qa
www.imdas.qa
www.imdads.qa
www.imdae.qa
www.imdade.qa
www.imdaed.qa
www.imdar.qa
www.imdadr.qa
www.imdard.qa
www.imdaf.qa
www.imdadf.qa
www.imdafd.qa
www.imdac.qa
www.imdadc.qa
www.imdacd.qa
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.