Smee.io Test Results

Smee.io Mobile Performance: 88/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 222 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.
Enable text compression
Potential savings of 196 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Eliminate render-blocking resources
Potential savings of 1,580 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.
Largest Contentful Paint element
2,940 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element

Smee.io Mobile SEO: 82/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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
21 errors 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.

Smee.io Mobile Best Practices: 83/100
Quick overview:
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.
Smee.io Mobile Accessibility: 82/100
Quick overview:
Contrast
These are opportunities to improve the legibility of your content.
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.
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.
Similar sites
Similar tests
www.smee.com
www.smee.net
www.smee.org
www.smee.info
www.smee.biz
www.smee.us
www.smee.mobi
www.mee.io
www.smee.io
www.wmee.io
www.swmee.io
www.wsmee.io
www.emee.io
www.semee.io
www.esmee.io
www.dmee.io
www.sdmee.io
www.dsmee.io
www.zmee.io
www.szmee.io
www.zsmee.io
www.xmee.io
www.sxmee.io
www.xsmee.io
www.amee.io
www.samee.io
www.asmee.io
www.see.io
www.snee.io
www.smnee.io
www.snmee.io
www.sjee.io
www.smjee.io
www.sjmee.io
www.skee.io
www.smkee.io
www.skmee.io
www.sme.io
www.smwe.io
www.smewe.io
www.smwee.io
www.smse.io
www.smese.io
www.smsee.io
www.smde.io
www.smede.io
www.smdee.io
www.smre.io
www.smere.io
www.smree.io
www.smew.io
www.smeew.io
www.smes.io
www.smees.io
www.smed.io
www.smeed.io
www.smer.io
www.smeer.io
Last Tested: