Goto.gg Test Results

Goto.gg Mobile Performance: 52/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
3.0 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
Eliminate render-blocking resources
Potential savings of 910 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.
Reduce unused JavaScript
Potential savings of 141 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.
Properly size images
Potential savings of 40 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce the impact of third-party code
Third-party code blocked the main thread for 510 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.
Serve images in next-gen formats
Potential savings of 83 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.
Largest Contentful Paint element
7,920 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid large layout shifts
6 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 JavaScript execution time
1.6 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.
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
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
Defer offscreen images
Potential savings of 90 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 28 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.
Serve static assets with an efficient cache policy
8 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Time to Interactive
8.4 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
250 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.

Goto.gg Mobile SEO: 85/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
3 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
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 how to make links crawlable

Goto.gg Mobile Best Practices: 62/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 about this errors in console diagnostic audit
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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.
Goto.gg Mobile Accessibility: 95/100
Quick overview:
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.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
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.
Similar sites
Similar tests
www.goto.com
www.goto.net
www.goto.org
www.goto.info
www.goto.biz
www.goto.us
www.goto.mobi
www.oto.gg
www.goto.gg
www.foto.gg
www.gfoto.gg
www.fgoto.gg
www.voto.gg
www.gvoto.gg
www.vgoto.gg
www.toto.gg
www.gtoto.gg
www.tgoto.gg
www.boto.gg
www.gboto.gg
www.bgoto.gg
www.yoto.gg
www.gyoto.gg
www.ygoto.gg
www.hoto.gg
www.ghoto.gg
www.hgoto.gg
www.gto.gg
www.gito.gg
www.goito.gg
www.gioto.gg
www.gkto.gg
www.gokto.gg
www.gkoto.gg
www.glto.gg
www.golto.gg
www.gloto.gg
www.gpto.gg
www.gopto.gg
www.gpoto.gg
www.goo.gg
www.goro.gg
www.gotro.gg
www.gorto.gg
www.gofo.gg
www.gotfo.gg
www.gofto.gg
www.gogo.gg
www.gotgo.gg
www.gogto.gg
www.goyo.gg
www.gotyo.gg
www.goyto.gg
www.got.gg
www.goti.gg
www.gotoi.gg
www.gotio.gg
www.gotk.gg
www.gotok.gg
www.gotko.gg
www.gotl.gg
www.gotol.gg
www.gotlo.gg
www.gotp.gg
www.gotop.gg
www.gotpo.gg
Last Tested: