Shor.by Site Title

Shor.

Shor.by Test Results

Shor.by Mobile Performance: 30/100
Quick overview:
First Meaningful Paint
13.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
22.0 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
690 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.
Server Backend Latencies
390 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Network Requests
Lists the network requests that were made during page load.
Script Treemap Data
Used for treemap app
Tasks
Lists the toplevel main thread tasks that executed during page load.
Network Round Trip Times
150 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Final Screenshot
The last screenshot captured of the pageload.

522022368270

Metrics
Collects all available metrics.
Diagnostics
Collection of useful page vitals.

Shor.by 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.
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.

Shor.by Mobile Best Practices: 83/100
Quick overview:
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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
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.
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
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Shor.by Mobile PWA: 78/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 about maskable manifest icons.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: Manifest does not have a PNG icon of at least 512px.
Shor.by Mobile Accessibility: 82/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.
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.
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 about the viewport meta tag.
Similar sites
Similar tests
www.shor.com
www.shor.net
www.shor.org
www.shor.info
www.shor.biz
www.shor.us
www.shor.mobi
www.hor.by
www.shor.by
www.whor.by
www.swhor.by
www.wshor.by
www.ehor.by
www.sehor.by
www.eshor.by
www.dhor.by
www.sdhor.by
www.dshor.by
www.zhor.by
www.szhor.by
www.zshor.by
www.xhor.by
www.sxhor.by
www.xshor.by
www.ahor.by
www.sahor.by
www.ashor.by
www.sor.by
www.sbor.by
www.shbor.by
www.sbhor.by
www.sgor.by
www.shgor.by
www.sghor.by
www.syor.by
www.shyor.by
www.syhor.by
www.suor.by
www.shuor.by
www.suhor.by
www.sjor.by
www.shjor.by
www.sjhor.by
www.snor.by
www.shnor.by
www.snhor.by
www.shr.by
www.shir.by
www.shoir.by
www.shior.by
www.shkr.by
www.shokr.by
www.shkor.by
www.shlr.by
www.sholr.by
www.shlor.by
www.shpr.by
www.shopr.by
www.shpor.by
www.sho.by
www.shoe.by
www.shore.by
www.shoer.by
www.shod.by
www.shord.by
www.shodr.by
www.shof.by
www.shorf.by
www.shofr.by
www.shot.by
www.short.by
www.shotr.by
Last Tested: