Jem.org Test Results
Jem.org Mobile Performance: 34/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,700 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 how to minimize third-party impact.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 40 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
Efficiently encode images
Potential savings of 315 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Avoid an excessive DOM size
931 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce JavaScript execution time
4.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Reduce unused CSS
Potential savings of 98 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.
Defer offscreen images
Potential savings of 613 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Largest Contentful Paint element
7,570 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 664 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 multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Eliminate render-blocking resources
Potential savings of 2,210 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.
Minimize main-thread work
10.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Serve images in next-gen formats
Potential savings of 805 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.
Minify JavaScript
Potential savings of 14 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Enable text compression
Potential savings of 480 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
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
Minify CSS
Potential savings of 11 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid enormous network payloads
Total size was 3,270 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Time to Interactive
19.3 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
700 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.
First Meaningful Paint
4.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Jem.org 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.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Jem.org Mobile Best Practices: 79/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
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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.
Jem.org Mobile Accessibility: 100/100
Quick overview:
Similar sites
Similar tests
www.jem.com
www.jem.net
www.jem.org
www.jem.info
www.jem.biz
www.jem.us
www.jem.mobi
www.em.org
www.jem.org
www.nem.org
www.jnem.org
www.njem.org
www.hem.org
www.jhem.org
www.hjem.org
www.uem.org
www.juem.org
www.ujem.org
www.iem.org
www.jiem.org
www.ijem.org
www.kem.org
www.jkem.org
www.kjem.org
www.mem.org
www.jmem.org
www.mjem.org
www.jm.org
www.jwm.org
www.jewm.org
www.jwem.org
www.jsm.org
www.jesm.org
www.jsem.org
www.jdm.org
www.jedm.org
www.jdem.org
www.jrm.org
www.jerm.org
www.jrem.org
www.je.org
www.jen.org
www.jemn.org
www.jenm.org
www.jej.org
www.jemj.org
www.jejm.org
www.jek.org
www.jemk.org
www.jekm.org
www.jem.net
www.jem.org
www.jem.info
www.jem.biz
www.jem.us
www.jem.mobi
www.em.org
www.jem.org
www.nem.org
www.jnem.org
www.njem.org
www.hem.org
www.jhem.org
www.hjem.org
www.uem.org
www.juem.org
www.ujem.org
www.iem.org
www.jiem.org
www.ijem.org
www.kem.org
www.jkem.org
www.kjem.org
www.mem.org
www.jmem.org
www.mjem.org
www.jm.org
www.jwm.org
www.jewm.org
www.jwem.org
www.jsm.org
www.jesm.org
www.jsem.org
www.jdm.org
www.jedm.org
www.jdem.org
www.jrm.org
www.jerm.org
www.jrem.org
www.je.org
www.jen.org
www.jemn.org
www.jenm.org
www.jej.org
www.jemj.org
www.jejm.org
www.jek.org
www.jemk.org
www.jekm.org