Wog.media Test Results
Wog.media Mobile Performance: 73/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused JavaScript
Potential savings of 182 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.
Avoid large layout shifts
4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Avoid multiple page redirects
Potential savings of 1,100 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
4,510 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Eliminate render-blocking resources
Potential savings of 1,060 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
Potential savings of 23 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
16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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
Avoid serving legacy JavaScript to modern browsers
Potential savings of 17 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
First Meaningful Paint
4.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
6.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
210 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Wog.media Mobile SEO: 75/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
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.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Wog.media Mobile Best Practices: 76/100
Quick overview:
User Experience
Document doesn't use legible font sizes
23.25% legible text
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 about legible font sizes.
General
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
Trust and Safety
Does not use HTTPS
1 insecure request 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.
Wog.media Mobile Accessibility: 87/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Similar sites
Similar tests
www.wog.com
www.wog.net
www.wog.org
www.wog.info
www.wog.biz
www.wog.us
www.wog.mobi
www.og.media
www.wog.media
www.qog.media
www.wqog.media
www.qwog.media
www.aog.media
www.waog.media
www.awog.media
www.sog.media
www.wsog.media
www.swog.media
www.eog.media
www.weog.media
www.ewog.media
www.wg.media
www.wig.media
www.woig.media
www.wiog.media
www.wkg.media
www.wokg.media
www.wkog.media
www.wlg.media
www.wolg.media
www.wlog.media
www.wpg.media
www.wopg.media
www.wpog.media
www.wo.media
www.wof.media
www.wogf.media
www.wofg.media
www.wov.media
www.wogv.media
www.wovg.media
www.wot.media
www.wogt.media
www.wotg.media
www.wob.media
www.wogb.media
www.wobg.media
www.woy.media
www.wogy.media
www.woyg.media
www.woh.media
www.wogh.media
www.wohg.media
www.wog.net
www.wog.org
www.wog.info
www.wog.biz
www.wog.us
www.wog.mobi
www.og.media
www.wog.media
www.qog.media
www.wqog.media
www.qwog.media
www.aog.media
www.waog.media
www.awog.media
www.sog.media
www.wsog.media
www.swog.media
www.eog.media
www.weog.media
www.ewog.media
www.wg.media
www.wig.media
www.woig.media
www.wiog.media
www.wkg.media
www.wokg.media
www.wkog.media
www.wlg.media
www.wolg.media
www.wlog.media
www.wpg.media
www.wopg.media
www.wpog.media
www.wo.media
www.wof.media
www.wogf.media
www.wofg.media
www.wov.media
www.wogv.media
www.wovg.media
www.wot.media
www.wogt.media
www.wotg.media
www.wob.media
www.wogb.media
www.wobg.media
www.woy.media
www.wogy.media
www.woyg.media
www.woh.media
www.wogh.media
www.wohg.media