Om4q.com Site Title

om4q.com

Om4q.com Test Results

Om4q.com Mobile Performance: 96/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Est savings of 170 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Enable text compression
Est savings of 28 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Serve static assets with an efficient cache policy
8 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Est savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Reduce unused JavaScript
Est savings of 47 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Document request latency
Est savings of 21 KiB
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Legacy JavaScript
Est savings of 31 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Use efficient cache lifetimes
Est savings of 285 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Improve image delivery
Est savings of 5 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Om4q.com Mobile SEO: 91/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 about the meta description.

Om4q.com Mobile Best Practices: 59/100
Quick overview:
Trust and Safety
Does not use HTTPS
9 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 served over 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 about HTTPS.
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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 about this errors in console diagnostic audit
Om4q.com Mobile Accessibility: 89/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 about the `lang` attribute.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar tests
www.om4q.com
www.om4q.net
www.om4q.org
www.om4q.info
www.om4q.biz
www.om4q.us
www.om4q.mobi
www.m4q.com
www.om4q.com
www.im4q.com
www.oim4q.com
www.iom4q.com
www.km4q.com
www.okm4q.com
www.kom4q.com
www.lm4q.com
www.olm4q.com
www.lom4q.com
www.pm4q.com
www.opm4q.com
www.pom4q.com
www.o4q.com
www.on4q.com
www.omn4q.com
www.onm4q.com
www.oj4q.com
www.omj4q.com
www.ojm4q.com
www.ok4q.com
www.omk4q.com
www.omq.com
www.om4.com
www.om4a.com
www.om4qa.com
www.om4aq.com
www.om4w.com
www.om4qw.com
www.om4wq.com
www.om4q.con
Last Tested: