Earth.org Test Results
Earth.org Mobile Performance: 35/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 290 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Efficiently encode images. Potential savings of 220 KiB
Optimized images load faster and consume less cellular data. Learn more.
Properly size images. Potential savings of 105 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused CSS. Potential savings of 23 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Remove unused JavaScript. Potential savings of 166 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,010 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
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.
Avoid an excessive DOM size
3,814 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Minimize main-thread work
6.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Serve static assets with an efficient cache policy
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid chaining critical requests
6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
59 requests • 1,534 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Earth.org Mobile SEO: 89/100
Quick overview:
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.
Tap targets are not sized appropriately
57% appropriately sized tap targets
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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Earth.org Mobile Best Practices: 69/100
Quick overview:
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
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.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
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 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.
Earth.org Mobile Progressive Web App: 89/100
Quick overview:
PWA Optimized
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.
Installable
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 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.
Earth.org Mobile Accessibility: 64/100
Quick overview:
Navigation
These are opportunities to improve keyboard navigation in your application.
`[id]` attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
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.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
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 more.
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-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn more.
ARIA IDs are not unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
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.
Similar sites
Similar tests
www.earth.com
www.earth.net
www.earth.org
www.earth.info
www.earth.biz
www.earth.us
www.earth.mobi
www.arth.org
www.earth.org
www.warth.org
www.ewarth.org
www.wearth.org
www.sarth.org
www.esarth.org
www.searth.org
www.darth.org
www.edarth.org
www.dearth.org
www.rarth.org
www.erarth.org
www.rearth.org
www.erth.org
www.eqrth.org
www.eaqrth.org
www.eqarth.org
www.ewrth.org
www.eawrth.org
www.esrth.org
www.easrth.org
www.ezrth.org
www.eazrth.org
www.ezarth.org
www.eath.org
www.eaeth.org
www.eareth.org
www.eaerth.org
www.eadth.org
www.eardth.org
www.eadrth.org
www.eafth.org
www.earfth.org
www.eafrth.org
www.eatth.org
www.eartth.org
www.eatrth.org
www.earh.org
www.earrh.org
www.eartrh.org
www.earrth.org
www.earfh.org
www.eartfh.org
www.eargh.org
www.eartgh.org
www.eargth.org
www.earyh.org
www.eartyh.org
www.earyth.org
www.eart.org
www.eartb.org
www.earthb.org
www.eartbh.org
www.eartg.org
www.earthg.org
www.earty.org
www.earthy.org
www.eartu.org
www.earthu.org
www.eartuh.org
www.eartj.org
www.earthj.org
www.eartjh.org
www.eartn.org
www.earthn.org
www.eartnh.org
www.earth.net
www.earth.org
www.earth.info
www.earth.biz
www.earth.us
www.earth.mobi
www.arth.org
www.earth.org
www.warth.org
www.ewarth.org
www.wearth.org
www.sarth.org
www.esarth.org
www.searth.org
www.darth.org
www.edarth.org
www.dearth.org
www.rarth.org
www.erarth.org
www.rearth.org
www.erth.org
www.eqrth.org
www.eaqrth.org
www.eqarth.org
www.ewrth.org
www.eawrth.org
www.esrth.org
www.easrth.org
www.ezrth.org
www.eazrth.org
www.ezarth.org
www.eath.org
www.eaeth.org
www.eareth.org
www.eaerth.org
www.eadth.org
www.eardth.org
www.eadrth.org
www.eafth.org
www.earfth.org
www.eafrth.org
www.eatth.org
www.eartth.org
www.eatrth.org
www.earh.org
www.earrh.org
www.eartrh.org
www.earrth.org
www.earfh.org
www.eartfh.org
www.eargh.org
www.eartgh.org
www.eargth.org
www.earyh.org
www.eartyh.org
www.earyth.org
www.eart.org
www.eartb.org
www.earthb.org
www.eartbh.org
www.eartg.org
www.earthg.org
www.earty.org
www.earthy.org
www.eartu.org
www.earthu.org
www.eartuh.org
www.eartj.org
www.earthj.org
www.eartjh.org
www.eartn.org
www.earthn.org
www.eartnh.org