Tools & Wizards About Us
fithaus.io screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

fithaus.io

FITHAUS - Unlock Your Potential With Top-Rated Personal Trainers

Page Load Speed

2.3 sec in total

First Response

167 ms

Resources Loaded

1.2 sec

Page Rendered

973 ms

fithaus.io screenshot

About Website

Visit fithaus.io now to see the best up-to-date FITHAUS content and also check out these interesting facts you probably never knew about fithaus.io

FITHAUS is an all-in-one solution for anyone looking to achieve their fitness goals. Our top-rated Personal Trainers come to you for 60-minute training sessions. Get personalized coaching and support ...

Visit fithaus.io

Key Findings

We analyzed Fithaus.io page load time and found that the first response time was 167 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

fithaus.io performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value3,350 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.192

64/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

fithaus.io

167 ms

www.fithaus.io

275 ms

styleSept11.css

68 ms

load.js

51 ms

bootstrap.min.css

44 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 67% of them (28 requests) were addressed to the original Fithaus.io, 12% (5 requests) were made to Maxcdn.bootstrapcdn.com and 5% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (618 ms) belongs to the original domain Fithaus.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.9 kB (2%)

Content Size

2.5 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fithaus.io 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. 60% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 37.7 kB

  • Original 51.2 kB
  • After minification 48.0 kB
  • After compression 13.5 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 37.7 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.4 MB
  • After minification 2.4 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. FITHAUS images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 289 B

  • Original 37.9 kB
  • After minification 37.9 kB
  • After compression 37.6 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.

CSS Optimization

-19%

Potential reduce by 3.9 kB

  • Original 20.5 kB
  • After minification 20.5 kB
  • After compression 16.5 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. Fithaus.io needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (46%)

Requests Now

37

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fithaus.io

fithaus.io

167 ms

www.fithaus.io

www.fithaus.io

275 ms

styleSept11.css

styleSept11.css

68 ms

load.js

load.js

51 ms

bootstrap.min.css

bootstrap.min.css

44 ms

classie.js

classie.js

145 ms

banner.js

banner.js

359 ms

jquery.min.js

jquery.min.js

49 ms

bootstrap.min.js

bootstrap.min.js

51 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

64 ms

counter.js

counter.js

207 ms

slick.min.js

slick.min.js

208 ms

modernizr-custom.js

modernizr-custom.js

208 ms

conversion.js

conversion.js

58 ms

bootstrap.min.css

bootstrap.min.css

32 ms

gtm.js

gtm.js

83 ms

fbevents.js

fbevents.js

30 ms

fithaus-black.svg

fithaus-black.svg

299 ms

Down_Arrow.png

Down_Arrow.png

263 ms

Stars_Img.png

Stars_Img.png

301 ms

Carousel_1.png

Carousel_1.png

434 ms

IMG_2913.jpg

IMG_2913.jpg

302 ms

Carousel_2.png

Carousel_2.png

433 ms

Carousel_3.png

Carousel_3.png

413 ms

Arrow.png

Arrow.png

301 ms

Barbell_1_ALT.webp

Barbell_1_ALT.webp

327 ms

w1-2_fithaus_feb10.webp

w1-2_fithaus_feb10.webp

489 ms

Slide_8.png

Slide_8.png

488 ms

grey-bg.png

grey-bg.png

374 ms

Slide_6.png

Slide_6.png

618 ms

Semi-Private_left.png

Semi-Private_left.png

543 ms

Semi-Private_Right.png

Semi-Private_Right.png

558 ms

bootstrap.min.css

bootstrap.min.css

38 ms

bootstrap.min.css

bootstrap.min.css

13 ms

Graphik-Regular-Web.woff

Graphik-Regular-Web.woff

240 ms

Graphik-Semibold-Web.woff

Graphik-Semibold-Web.woff

296 ms

GT-America-Compressed-Bold.woff

GT-America-Compressed-Bold.woff

304 ms

51 ms

Barbell_1_ALT.png

Barbell_1_ALT.png

236 ms

w1-2_fithaus_feb10.jpg

w1-2_fithaus_feb10.jpg

280 ms

28 ms

halucbmi

halucbmi

31 ms

Accessibility Review

fithaus.io accessibility score

81

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

fithaus.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fithaus.io SEO score

79

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Fithaus.io 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 Fithaus.io 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

fithaus.io

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