Access footlevelers.com. Custom Orthotic Insoles

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value5.6 s

54/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.335

34/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

footlevelers.com

57 ms

www.footlevelers.com

146 ms

visitor.css.aspx

27 ms

styles.css

55 ms

bx_styles.css

27 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 67% of them (34 requests) were addressed to the original Footlevelers.com, 6% (3 requests) were made to Pixel-geo.prfct.co and 6% (3 requests) were made to Pixel.prfct.co. The less responsive or slowest element that took the longest time to load (850 ms) relates to the external source Pixel.rubiconproject.com.

Content Size

2.5 MB

After Optimization

1.8 MB

In fact, the total size of Footlevelers.com main page is 2.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.7 kB

Original 33.0 kB
After minification 26.6 kB
After compression 8.3 kB

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. This page needs HTML code to be minified as it can gain 6.3 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.7 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 51.9 kB

Original 1.7 MB
After minification 1.6 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Footlevelers images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 592.1 kB

Original 772.7 kB
After minification 626.8 kB
After compression 180.7 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 592.1 kB or 77% of the original size.

CSS Optimization

-81%

Potential reduce by 50.9 kB

Original 62.8 kB
After minification 61.3 kB
After compression 11.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Footlevelers.com needs all CSS files to be minified and compressed as it can save up to 50.9 kB or 81% of the original size.

Requests Now

After Optimization

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Footlevelers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

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

High

Links are not crawlable

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 uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Footlevelers.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Footlevelers.com 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 Footlevelers. 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: