Tools & Wizards About Us
fitlist.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fitlist.com

Fitlist – Workout Log & Planner App, Personal Training Software

Page Load Speed

9.2 sec in total

First Response

1.5 sec

Resources Loaded

6.6 sec

Page Rendered

1 sec

fitlist.com screenshot

About Website

Visit fitlist.com now to see the best up-to-date Fitlist content and also check out these interesting facts you probably never knew about fitlist.com

Visit fitlist.com

Key Findings

We analyzed Fitlist.com page load time and found that the first response time was 1.5 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fitlist.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value36.8 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value31.6 s

0/100

10%

Network Requests Diagram

www.fitlist.com

1547 ms

formidableforms.css

255 ms

icons.css

223 ms

global.css

195 ms

mediaelementplayer-legacy.min.css

202 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 79% of them (78 requests) were addressed to the original Fitlist.com, 16% (16 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Import.themovation.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Fitlist.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (18%)

Content Size

9.3 MB

After Optimization

7.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fitlist.com main page is 9.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. 60% of websites need less resources to load. Images take 8.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 109.4 kB

  • Original 128.1 kB
  • After minification 120.5 kB
  • After compression 18.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. 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 109.4 kB or 85% of the original size.

Image Optimization

-15%

Potential reduce by 1.3 MB

  • Original 8.6 MB
  • After minification 7.2 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. Obviously, Fitlist needs image optimization as it can save up to 1.3 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-24%

Potential reduce by 64.9 kB

  • Original 267.7 kB
  • After minification 267.7 kB
  • After compression 202.8 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 64.9 kB or 24% of the original size.

CSS Optimization

-42%

Potential reduce by 128.7 kB

  • Original 307.7 kB
  • After minification 300.2 kB
  • After compression 178.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. Fitlist.com needs all CSS files to be minified and compressed as it can save up to 128.7 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (74%)

Requests Now

73

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fitlist.com

www.fitlist.com

1547 ms

formidableforms.css

formidableforms.css

255 ms

icons.css

icons.css

223 ms

global.css

global.css

195 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

202 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

201 ms

header-footer-elementor.css

header-footer-elementor.css

202 ms

elementor-icons.min.css

elementor-icons.min.css

269 ms

frontend.min.css

frontend.min.css

284 ms

swiper.min.css

swiper.min.css

278 ms

e-swiper.min.css

e-swiper.min.css

269 ms

post-454.css

post-454.css

286 ms

frontend.min.css

frontend.min.css

417 ms

all.min.css

all.min.css

400 ms

v4-shims.min.css

v4-shims.min.css

339 ms

global.css

global.css

349 ms

animations.min.css

animations.min.css

372 ms

post-606.css

post-606.css

366 ms

post-288.css

post-288.css

409 ms

frontend.css

frontend.css

436 ms

font-awesome.min.css

font-awesome.min.css

439 ms

app.css

app.css

513 ms

style.css

style.css

464 ms

css

css

54 ms

fontawesome.min.css

fontawesome.min.css

548 ms

solid.min.css

solid.min.css

488 ms

regular.min.css

regular.min.css

509 ms

brands.min.css

brands.min.css

507 ms

v4-shims.min.js

v4-shims.min.js

531 ms

jquery.min.js

jquery.min.js

575 ms

jquery-migrate.min.js

jquery-migrate.min.js

593 ms

widget-heading.min.css

widget-heading.min.css

459 ms

widget-image.min.css

widget-image.min.css

547 ms

widget-spacer.min.css

widget-spacer.min.css

548 ms

widget-icon-list.min.css

widget-icon-list.min.css

549 ms

widget-image-carousel.min.css

widget-image-carousel.min.css

550 ms

widget-counter.min.css

widget-counter.min.css

549 ms

widget-icon-box.min.css

widget-icon-box.min.css

549 ms

widget-testimonial.min.css

widget-testimonial.min.css

484 ms

widget-text-editor.min.css

widget-text-editor.min.css

479 ms

widget-social-icons.min.css

widget-social-icons.min.css

511 ms

apple-webkit.min.css

apple-webkit.min.css

515 ms

themo-foot.js

themo-foot.js

504 ms

vendor_footer.js

vendor_footer.js

524 ms

main.js

main.js

510 ms

jquery-numerator.min.js

jquery-numerator.min.js

484 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

546 ms

webpack.runtime.min.js

webpack.runtime.min.js

541 ms

frontend-modules.min.js

frontend-modules.min.js

540 ms

hooks.min.js

hooks.min.js

487 ms

i18n.min.js

i18n.min.js

498 ms

frontend.min.js

frontend.min.js

481 ms

core.min.js

core.min.js

494 ms

frontend.min.js

frontend.min.js

471 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

534 ms

app_store_button.png

app_store_button.png

123 ms

Logo-1-reverse-175x50.png

Logo-1-reverse-175x50.png

269 ms

bigstock-Rod-with-weights-in-the-gym-93546473.png

bigstock-Rod-with-weights-in-the-gym-93546473.png

713 ms

iphone-watch-web.png

iphone-watch-web.png

539 ms

3.png

3.png

731 ms

2.png

2.png

440 ms

1-1.png

1-1.png

572 ms

2-1.png

2-1.png

544 ms

4.png

4.png

579 ms

5.png

5.png

668 ms

Watch_photorealistic_mockup.png

Watch_photorealistic_mockup.png

675 ms

Coach-type.png

Coach-type.png

655 ms

The_New_York_Times_logo-1024x151.png

The_New_York_Times_logo-1024x151.png

655 ms

google_play_button.png

google_play_button.png

110 ms

tv.png

tv.png

671 ms

comac.jpeg

comac.jpeg

670 ms

Logo-1-reverse.png

Logo-1-reverse.png

680 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

1469 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

1637 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

64 ms

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

1719 ms

S6u9w4BMUTPHh7USSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh7USSwaPHw3q5d0N7w.woff

1738 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

86 ms

S6u8w4BMUTPHh30AXC-s.woff

S6u8w4BMUTPHh30AXC-s.woff

108 ms

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

1624 ms

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

1651 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

110 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

108 ms

S6u8w4BMUTPHjxsAXC-s.woff

S6u8w4BMUTPHjxsAXC-s.woff

109 ms

S6u_w4BMUTPHjxsI9w2_Gwfr.woff

S6u_w4BMUTPHjxsI9w2_Gwfr.woff

108 ms

S6u-w4BMUTPHjxsIPx-oPCQ.woff

S6u-w4BMUTPHjxsIPx-oPCQ.woff

107 ms

S6u_w4BMUTPHjxsI5wq_Gwfr.woff

S6u_w4BMUTPHjxsI5wq_Gwfr.woff

110 ms

S6u_w4BMUTPHjxsI3wi_Gwfr.woff

S6u_w4BMUTPHjxsI3wi_Gwfr.woff

110 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

110 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

111 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

111 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

110 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

111 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

111 ms

fa-solid-900.woff

fa-solid-900.woff

1531 ms

api.min.js

api.min.js

60 ms

fa-regular-400.woff

fa-regular-400.woff

1604 ms

fa-brands-400.woff

fa-brands-400.woff

1645 ms

beacon-v2.helpscout.net

beacon-v2.helpscout.net

20 ms

Accessibility Review

fitlist.com accessibility score

86

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

Links do not have a discernible name

Best Practices

fitlist.com 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

fitlist.com SEO score

93

Search Engine Optimization Advices

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 Fitlist.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 Fitlist.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

fitlist.com

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