Tools & Wizards About Us
fitty.co screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

fitty.co

Fitty - Track workouts, analze fitness graphs and boost your progress!

Page Load Speed

1.9 sec in total

First Response

39 ms

Resources Loaded

1.6 sec

Page Rendered

261 ms

fitty.co screenshot

About Website

Visit fitty.co now to see the best up-to-date Fitty content and also check out these interesting facts you probably never knew about fitty.co

Fitty. Your personal fitness dashboard.

Visit fitty.co

Key Findings

We analyzed Fitty.co page load time and found that the first response time was 39 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

fitty.co performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

Network Requests Diagram

fitty.co

39 ms

fitty.co

326 ms

font-awesome.min.css

30 ms

jquery.min.js

413 ms

reset.css

224 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 92% of them (48 requests) were addressed to the original Fitty.co, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to 0. The less responsive or slowest element that took the longest time to load (783 ms) belongs to the original domain Fitty.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.8 kB (15%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fitty.co main page is 1.3 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 11.4 kB

  • Original 15.1 kB
  • After minification 12.4 kB
  • After compression 3.7 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 2.7 kB, which is 18% 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 11.4 kB or 75% of the original size.

Image Optimization

-13%

Potential reduce by 136.0 kB

  • Original 1.1 MB
  • After minification 945.1 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. Obviously, Fitty needs image optimization as it can save up to 136.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 39.9 kB

  • Original 173.4 kB
  • After minification 173.4 kB
  • After compression 133.4 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 39.9 kB or 23% of the original size.

CSS Optimization

-25%

Potential reduce by 1.4 kB

  • Original 5.9 kB
  • After minification 5.9 kB
  • After compression 4.4 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. Fitty.co needs all CSS files to be minified and compressed as it can save up to 1.4 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (29%)

Requests Now

49

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fitty.co

fitty.co

39 ms

fitty.co

fitty.co

326 ms

font-awesome.min.css

font-awesome.min.css

30 ms

jquery.min.js

jquery.min.js

413 ms

reset.css

reset.css

224 ms

grid.css

grid.css

221 ms

style.css

style.css

297 ms

prototype.js

prototype.js

412 ms

scriptaculous.js

scriptaculous.js

381 ms

sizzle.js

sizzle.js

333 ms

smoothscroll.js

smoothscroll.js

327 ms

jquery.easing.js

jquery.easing.js

307 ms

jquery.scrollto.min.js

jquery.scrollto.min.js

385 ms

jquery.localscroll.min.js

jquery.localscroll.min.js

386 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

391 ms

waypoints.min.js

waypoints.min.js

412 ms

loupe.js

loupe.js

425 ms

notifications.js

notifications.js

428 ms

init.js

init.js

450 ms

analytics.js

analytics.js

56 ms

mobile-nav.png

mobile-nav.png

153 ms

logo.svg

logo.svg

151 ms

hero-hardware.jpg

hero-hardware.jpg

260 ms

design.png

design.png

178 ms

setup.png

setup.png

182 ms

documentation.png

documentation.png

207 ms

sidephone-small.png

sidephone-small.png

244 ms

sidephone-big.png

sidephone-big.png

343 ms

static-tablet.jpg

static-tablet.jpg

281 ms

static-phone.png

static-phone.png

292 ms

apple.png

apple.png

312 ms

android.png

android.png

344 ms

windows.png

windows.png

360 ms

loupe.png

loupe.png

384 ms

detail-small.png

detail-small.png

395 ms

placeholder.png

placeholder.png

783 ms

screen1.jpg

screen1.jpg

448 ms

screen2.jpg

screen2.jpg

447 ms

screen3.jpg

screen3.jpg

460 ms

screen4.jpg

screen4.jpg

485 ms

screen5.jpg

screen5.jpg

518 ms

screen6.jpg

screen6.jpg

549 ms

collect

collect

13 ms

js

js

62 ms

loading.gif

loading.gif

475 ms

hardware.jpg

hardware.jpg

486 ms

prev.png

prev.png

476 ms

next.png

next.png

508 ms

pager.png

pager.png

537 ms

loupedisplacementmap.png

loupedisplacementmap.png

552 ms

pager-active.png

pager-active.png

149 ms

detail-big.jpg

detail-big.jpg

195 ms

Accessibility Review

fitty.co accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

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

fitty.co best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fitty.co SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 Fitty.co 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 Fitty.co 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

fitty.co

Open Graph description is not detected on the main page of Fitty. 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: