Tools & Wizards About Us
edge.fit screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

edge.fit

EDGE Fitness & Strength - Gym - Indianapolis, Indiana

Page Load Speed

1.2 sec in total

First Response

60 ms

Resources Loaded

640 ms

Page Rendered

497 ms

edge.fit screenshot

About Website

Click here to check amazing EDGE content. Otherwise, check out these important facts you probably never knew about edge.fit

We're a locally owned, all-inclusive gym that's built on community. We specialize in helping busy professionals & parents prioritize their health and fitness.

Visit edge.fit

Key Findings

We analyzed Edge.fit page load time and found that the first response time was 60 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

edge.fit performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value1,720 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

edge.fit

60 ms

qt=q:95

136 ms

script.js

89 ms

UX.4.36.0.js

24 ms

script.js

68 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 11% of them (1 request) were addressed to the original Edge.fit, 89% (8 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (553 ms) relates to the external source Img1.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.6 kB (7%)

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Edge.fit main page is 1.1 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. Only 10% of websites need less resources to load. Images take 905.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 80.4 kB

  • Original 97.3 kB
  • After minification 97.2 kB
  • After compression 16.8 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. 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 80.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 77 B

  • Original 905.3 kB
  • After minification 905.3 kB

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. EDGE images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 28 B

  • Original 139.0 kB
  • After minification 139.0 kB
  • After compression 138.9 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 Breakdown

Number of requests can be reduced by 3 (43%)

Requests Now

7

After Optimization

4

  • Images
  • JavaScript

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

Network Requests Diagram

edge.fit

edge.fit

60 ms

qt=q:95

qt=q:95

136 ms

script.js

script.js

89 ms

UX.4.36.0.js

UX.4.36.0.js

24 ms

script.js

script.js

68 ms

rs=w:1920,m

rs=w:1920,m

340 ms

rs=w:1920,m

rs=w:1920,m

553 ms

scc-c2.min.js

scc-c2.min.js

4 ms

HTxqL289NzCGg4MzN6KJ7eW6CYyF-A.woff

HTxqL289NzCGg4MzN6KJ7eW6CYyF-A.woff

5 ms

Accessibility Review

edge.fit accessibility score

88

Accessibility Issues

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.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

edge.fit best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

edge.fit SEO score

89

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Edge.fit 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 Edge.fit 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

edge.fit

Open Graph data is detected on the main page of EDGE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: