Access otleyrun.net. otleyrun.net - otleyrun Resources and Information.

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

99/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.227

55/100

15%

TTI (Time to Interactive)

Value4.3 s

85/100

10%

otleyrun.net

248 ms

iife.min.js

158 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Otleyrun.net and no external sources were called. The less responsive or slowest element that took the longest time to load (248 ms) belongs to the original domain Otleyrun.net.

Content Size

15.4 kB

After Optimization

14.9 kB

In fact, the total size of Otleyrun.net main page is 15.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. Javascripts take 14.3 kB which makes up the majority of the site volume.

HTML Optimization

-46%

Potential reduce by 476 B

Original 1.0 kB
After minification 1.0 kB
After compression 562 B

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 476 B or 46% of the original size.

JavaScript Optimization

-0%

Potential reduce by 12 B

Original 14.3 kB
After minification 14.3 kB
After compression 14.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Now

After Optimization

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otleyrun. According to our analytics all requests are already optimized.

Accessibility Issues

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.

High

<frame> or <iframe> elements do not have a title

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document doesn't use legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otleyrun.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Otleyrun.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Otleyrun. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: