Beth.games Test Results

Beth.games Mobile Performance: 9/100
Quick overview:
Max Potential First Input Delay
880 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.
Time to Interactive
12.5 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid large layout shifts
9 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
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,040 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.
Minimize main-thread work
8.7 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
Avoid multiple page redirects
Potential savings of 2,320 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce JavaScript execution time
6.2 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 JavaScript
Potential savings of 315 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.
Eliminate render-blocking resources
Potential savings of 300 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
12,450 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Preload Largest Contentful Paint image
Potential savings of 750 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Defer offscreen images
Potential savings of 106 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.
Reduce unused CSS
Potential savings of 91 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.
Efficiently encode images
Potential savings of 904 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve static assets with an efficient cache policy
67 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
Properly size images
Potential savings of 26 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 7 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
Avoid enormous network payloads
Total size was 5,085 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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`.
Serve images in next-gen formats
Potential savings of 3,167 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.

Beth.games Mobile SEO: 75/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Links do not have descriptive text
8 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
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. Description text is empty.

Beth.games Mobile Best Practices: 83/100
Quick overview:
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.
Beth.games Mobile Accessibility: 88/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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
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 how to make buttons more accessible.
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.
Similar tests
www.beth.com
www.beth.net
www.beth.org
www.beth.info
www.beth.biz
www.beth.us
www.beth.mobi
www.eth.games
www.beth.games
www.veth.games
www.bveth.games
www.vbeth.games
www.geth.games
www.bgeth.games
www.gbeth.games
www.heth.games
www.bheth.games
www.hbeth.games
www.neth.games
www.bneth.games
www.nbeth.games
www.bth.games
www.bwth.games
www.bewth.games
www.bweth.games
www.bsth.games
www.besth.games
www.bseth.games
www.bdth.games
www.bedth.games
www.bdeth.games
www.brth.games
www.berth.games
www.breth.games
www.beh.games
www.berh.games
www.betrh.games
www.befh.games
www.betfh.games
www.befth.games
www.begh.games
www.betgh.games
www.begth.games
www.beyh.games
www.betyh.games
www.beyth.games
www.bet.games
www.betb.games
www.bethb.games
www.betbh.games
www.betg.games
www.bethg.games
www.bety.games
www.bethy.games
www.betu.games
www.bethu.games
www.betuh.games
www.betj.games
www.bethj.games
www.betjh.games
www.betn.games
www.bethn.games
www.betnh.games
Last Tested: