Tools & Wizards About Us
fullfact.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fullfact.com

DECIDE4ACTION

Page Load Speed

4.2 sec in total

First Response

59 ms

Resources Loaded

3.2 sec

Page Rendered

891 ms

fullfact.com screenshot

About Website

Click here to check amazing Fullfact content. Otherwise, check out these important facts you probably never knew about fullfact.com

Improve what you cannot see - Decide4Action offers the best OEE solution to help your company improve its production performance.

Visit fullfact.com

Key Findings

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

Performance Metrics

fullfact.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value2,850 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.216

58/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

fullfact.com

59 ms

fullfact.com

342 ms

355 ms

override_custom.css

67 ms

css2

49 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Fullfact.com, 49% (40 requests) were made to Decide4action.com and 14% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.5 kB (9%)

Content Size

3.0 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fullfact.com main page is 3.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 91.1 kB

  • Original 113.3 kB
  • After minification 111.4 kB
  • After compression 22.2 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 91.1 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 61.4 kB

  • Original 2.2 MB
  • After minification 2.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. Fullfact images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 101.2 kB

  • Original 517.5 kB
  • After minification 517.5 kB
  • After compression 416.3 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 101.2 kB or 20% of the original size.

CSS Optimization

-28%

Potential reduce by 25.9 kB

  • Original 92.4 kB
  • After minification 92.4 kB
  • After compression 66.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. Fullfact.com needs all CSS files to be minified and compressed as it can save up to 25.9 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (77%)

Requests Now

64

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fullfact.com

fullfact.com

59 ms

fullfact.com

fullfact.com

342 ms

355 ms

override_custom.css

override_custom.css

67 ms

css2

css2

49 ms

slick.css

slick.css

130 ms

slick-theme.css

slick-theme.css

189 ms

styles.css

styles.css

190 ms

styles.css

styles.css

189 ms

css

css

69 ms

style.css

style.css

252 ms

page-builder.css

page-builder.css

260 ms

settings.css

settings.css

193 ms

styles.min.css

styles.min.css

250 ms

style.min.css

style.min.css

252 ms

style-core.css

style-core.css

255 ms

gdlr-style-custom.css

gdlr-style-custom.css

266 ms

ytprefs.min.css

ytprefs.min.css

313 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

33 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

438 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

335 ms

app.js

app.js

378 ms

js

js

82 ms

ytprefs.min.js

ytprefs.min.js

335 ms

script-new.js

script-new.js

335 ms

slick.js

slick.js

535 ms

index.js

index.js

375 ms

index.js

index.js

376 ms

script.js

script.js

540 ms

page-builder.js

page-builder.js

536 ms

5315011.js

5315011.js

115 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

537 ms

effect.min.js

effect.min.js

537 ms

script-core.js

script-core.js

538 ms

fitvids.min.js

fitvids.min.js

538 ms

wp-consent-api.min.js

wp-consent-api.min.js

539 ms

gtm.js

gtm.js

265 ms

new-logo.png

new-logo.png

244 ms

D4A-Website-Image-3.png

D4A-Website-Image-3.png

448 ms

D4A-Website-Image-6.png

D4A-Website-Image-6.png

249 ms

OEE-Graphic.png

OEE-Graphic.png

244 ms

D4A-PageToolkit-1.png

D4A-PageToolkit-1.png

446 ms

OEE-Production-Graph.png

OEE-Production-Graph.png

244 ms

OEE-Production-Graph.png

OEE-Production-Graph.png

246 ms

footer-logo.svg

footer-logo.svg

246 ms

Decide4ction_Consulting_Reverse_Color-1024x620.png

Decide4ction_Consulting_Reverse_Color-1024x620.png

323 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

320 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

813 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

1028 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

955 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

953 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

1028 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

232 ms

ElegantIcons.woff

ElegantIcons.woff

231 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf

1013 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf

1027 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf

1096 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf

1075 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf

1096 ms

analytics.js

analytics.js

774 ms

insight.min.js

insight.min.js

847 ms

destination

destination

410 ms

js

js

555 ms

fbevents.js

fbevents.js

783 ms

4cc4b94980124a2f9cbd1cad4d53e47a.js.ubembed.com

4cc4b94980124a2f9cbd1cad4d53e47a.js.ubembed.com

910 ms

web-interactives-embed.js

web-interactives-embed.js

771 ms

collectedforms.js

collectedforms.js

806 ms

fb.js

fb.js

775 ms

5315011.js

5315011.js

806 ms

5315011.js

5315011.js

769 ms

loader.js

loader.js

437 ms

380 ms

landing

landing

354 ms

collect

collect

208 ms

collect

collect

169 ms

537527730099265

537527730099265

255 ms

bundle.js

bundle.js

86 ms

call-tracking_9.js

call-tracking_9.js

9 ms

22 ms

wcm

wcm

16 ms

zi-tag.js

zi-tag.js

74 ms

Accessibility Review

fullfact.com accessibility score

90

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.

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

fullfact.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Page has valid source maps

SEO Factors

fullfact.com SEO score

100

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

fullfact.com

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