Tools & Wizards About Us
fightingfatigue.org screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fightingfatigue.org

Chronic Fatigue Syndrome - Chronic Fatigue Syndrome, Fibromyalgia, and IC Disease

Page Load Speed

929 ms in total

First Response

193 ms

Resources Loaded

622 ms

Page Rendered

114 ms

fightingfatigue.org screenshot

About Website

Click here to check amazing Fighting Fatigue content for United States. Otherwise, check out these important facts you probably never knew about fightingfatigue.org

Chronic Fatigue Syndrome, Fibromyalgia, and IC Disease

Visit fightingfatigue.org

Key Findings

We analyzed Fightingfatigue.org page load time and found that the first response time was 193 ms and then it took 736 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

fightingfatigue.org performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

82/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value1,470 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.338

33/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

fightingfatigue.org

193 ms

wp-emoji-release.min.js

33 ms

style.css

58 ms

style.min.css

86 ms

style.css

60 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 65% of them (20 requests) were addressed to the original Fightingfatigue.org, 6% (2 requests) were made to Pagead2.googlesyndication.com and 6% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (246 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.2 kB (11%)

Content Size

393.7 kB

After Optimization

350.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fightingfatigue.org main page is 393.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 241.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 32.3 kB

  • Original 42.3 kB
  • After minification 41.9 kB
  • After compression 10.0 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 32.3 kB or 76% of the original size.

Image Optimization

-10%

Potential reduce by 10.5 kB

  • Original 110.2 kB
  • After minification 99.6 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. Fighting Fatigue images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 430 B

  • Original 241.3 kB
  • After minification 241.3 kB
  • After compression 240.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 22 (81%)

Requests Now

27

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fightingfatigue.org

fightingfatigue.org

193 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

33 ms

style.css

style.css

58 ms

style.min.css

style.min.css

86 ms

style.css

style.css

60 ms

dashicons.min.css

dashicons.min.css

91 ms

css

css

21 ms

jquery.min.js

jquery.min.js

96 ms

jquery-migrate.min.js

jquery-migrate.min.js

62 ms

adsbygoogle.js

adsbygoogle.js

112 ms

brand

brand

9 ms

jstree.min.js

jstree.min.js

151 ms

jstree.state.js

jstree.state.js

87 ms

public.js

public.js

92 ms

hoverIntent.min.js

hoverIntent.min.js

151 ms

superfish.min.js

superfish.min.js

151 ms

superfish.args.min.js

superfish.args.min.js

151 ms

skip-links.min.js

skip-links.min.js

154 ms

jquery.matchHeight.min.js

jquery.matchHeight.min.js

154 ms

global.js

global.js

154 ms

responsive-menus.min.js

responsive-menus.min.js

153 ms

jscripts-ftr2-min.js

jscripts-ftr2-min.js

153 ms

brandjs.js

brandjs.js

17 ms

cropped-fightingfatigue520.png

cropped-fightingfatigue520.png

102 ms

nmedianet.js

nmedianet.js

135 ms

show_ads_impl.js

show_ads_impl.js

246 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

43 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

42 ms

bping.php

bping.php

112 ms

smtr

smtr

65 ms

branding.png

branding.png

18 ms

Accessibility Review

fightingfatigue.org accessibility score

87

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

fightingfatigue.org 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

fightingfatigue.org SEO score

92

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

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 Fightingfatigue.org 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 Fightingfatigue.org 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

fightingfatigue.org

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