Fotw.net Site Title

FOTW

Fotw.net Test Results

Fotw.net Mobile Performance: 65/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused CSS
Potential savings of 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Largest Contentful Paint element
9,660 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 2,370 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.
Minify CSS
Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Serve images in next-gen formats
Potential savings of 925 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
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`.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
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
Properly size images
Potential savings of 46 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Efficiently encode images
Potential savings of 48 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve static assets with an efficient cache policy
45 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
First Meaningful Paint
5.1 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
5.1 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.

Fotw.net Mobile SEO: 92/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.

Fotw.net Mobile Best Practices: 76/100
Quick overview:
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Trust and Safety
Does not use HTTPS
14 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.
Fotw.net Mobile Accessibility: 79/100
Quick overview:
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
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 `progressbar` elements do not have accessible names.
When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar sites
Similar tests
www.fotw.com
www.fotw.net
www.fotw.org
www.fotw.info
www.fotw.biz
www.fotw.us
www.fotw.mobi
www.otw.net
www.fotw.net
www.cotw.net
www.fcotw.net
www.cfotw.net
www.dotw.net
www.fdotw.net
www.dfotw.net
www.rotw.net
www.frotw.net
www.rfotw.net
www.totw.net
www.ftotw.net
www.tfotw.net
www.gotw.net
www.fgotw.net
www.gfotw.net
www.votw.net
www.fvotw.net
www.vfotw.net
www.ftw.net
www.fitw.net
www.foitw.net
www.fiotw.net
www.fktw.net
www.foktw.net
www.fkotw.net
www.fltw.net
www.foltw.net
www.flotw.net
www.fptw.net
www.foptw.net
www.fpotw.net
www.fow.net
www.forw.net
www.fotrw.net
www.fortw.net
www.fofw.net
www.fotfw.net
www.foftw.net
www.fogw.net
www.fotgw.net
www.fogtw.net
www.foyw.net
www.fotyw.net
www.foytw.net
www.fot.net
www.fotq.net
www.fotwq.net
www.fotqw.net
www.fota.net
www.fotwa.net
www.fotaw.net
www.fots.net
www.fotws.net
www.fotsw.net
www.fote.net
www.fotwe.net
www.fotew.net
Last Tested: