Shory.com Test Results

Shory.com Mobile Performance: 35/100
Quick overview:
Max Potential First Input Delay
650 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
10.9 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.
Reduce initial server response time
Root document took 680 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Reduce JavaScript execution time
3.3 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 164 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.
Minify CSS
Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Largest Contentful Paint element
4,680 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid large layout shifts
4 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
Properly size images
Potential savings of 1,268 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
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.
Reduce unused CSS
Potential savings of 18 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,420 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.
Eliminate render-blocking resources
Potential savings of 160 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
6.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 minimize main-thread work
Avoid serving legacy JavaScript to modern browsers
Potential savings of 10 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
Defer offscreen images
Potential savings of 40 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.
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
Serve static assets with an efficient cache policy
36 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 4,127 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`.

Shory.com 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
1 link 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

Shory.com Mobile Best Practices: 79/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
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.
Shory.com Mobile Accessibility: 99/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 have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Similar sites
Similar tests
www.shory.com
www.shory.net
www.shory.org
www.shory.info
www.shory.biz
www.shory.us
www.shory.mobi
www.hory.com
www.shory.com
www.whory.com
www.swhory.com
www.wshory.com
www.ehory.com
www.sehory.com
www.eshory.com
www.dhory.com
www.sdhory.com
www.dshory.com
www.zhory.com
www.szhory.com
www.zshory.com
www.xhory.com
www.sxhory.com
www.xshory.com
www.ahory.com
www.sahory.com
www.ashory.com
www.sory.com
www.sbory.com
www.shbory.com
www.sbhory.com
www.sgory.com
www.shgory.com
www.sghory.com
www.syory.com
www.shyory.com
www.syhory.com
www.suory.com
www.shuory.com
www.suhory.com
www.sjory.com
www.shjory.com
www.sjhory.com
www.snory.com
www.shnory.com
www.snhory.com
www.shry.com
www.shiry.com
www.shoiry.com
www.shiory.com
www.shkry.com
www.shokry.com
www.shkory.com
www.shlry.com
www.sholry.com
www.shlory.com
www.shpry.com
www.shopry.com
www.shpory.com
www.shoy.com
www.shoey.com
www.shorey.com
www.shoery.com
www.shody.com
www.shordy.com
www.shodry.com
www.shofy.com
www.shorfy.com
www.shofry.com
www.shoty.com
www.shorty.com
www.shotry.com
www.shor.com
www.short.com
www.shoryt.com
www.shorg.com
www.shoryg.com
www.shorgy.com
www.shorh.com
www.shoryh.com
www.shorhy.com
www.shoru.com
www.shoryu.com
www.shoruy.com
www.shory.con
Last Tested: