Tools & Wizards About Us
fyreguard.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fyreguard.com

Fire Protection Systems – Fyreguard Passive Fire Protection Solutions

Page Load Speed

7.2 sec in total

First Response

714 ms

Resources Loaded

6.2 sec

Page Rendered

285 ms

fyreguard.com screenshot

About Website

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

Fire protection problems in commercial, industrial, civil, healthcare and special purpose buildings are covered by approved Fyreguard Passive FireProtection Systems. We work with Architects, Engineers...

Visit fyreguard.com

Key Findings

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

Performance Metrics

fyreguard.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

fyreguard.com

714 ms

fyreguard.com

950 ms

www.fyreguard.com

950 ms

www.fyreguard.com

1457 ms

app.css

471 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 77% of them (27 requests) were addressed to the original Fyreguard.com, 9% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Fyreguard.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 21.4 kB (4%)

Content Size

485.8 kB

After Optimization

464.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fyreguard.com main page is 485.8 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. 30% of websites need less resources to load. Images take 345.1 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 9.9 kB

  • Original 13.6 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. 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 9.9 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 3.7 kB

  • Original 345.1 kB
  • After minification 341.3 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. Fyreguard images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 2.9 kB

  • Original 93.9 kB
  • After minification 93.7 kB
  • After compression 91.0 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

-14%

Potential reduce by 4.8 kB

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

Requests Breakdown

Number of requests can be reduced by 9 (33%)

Requests Now

27

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fyreguard.com

fyreguard.com

714 ms

fyreguard.com

fyreguard.com

950 ms

www.fyreguard.com

www.fyreguard.com

950 ms

www.fyreguard.com

www.fyreguard.com

1457 ms

app.css

app.css

471 ms

css

css

32 ms

font-awesome.min.css

font-awesome.min.css

700 ms

modernizr.js

modernizr.js

706 ms

js

js

76 ms

jquery.min.js

jquery.min.js

955 ms

foundation.min.js

foundation.min.js

954 ms

foundation.abide.js

foundation.abide.js

748 ms

foundation.magellan.js

foundation.magellan.js

749 ms

foundation.topbar.js

foundation.topbar.js

954 ms

app.js

app.js

952 ms

logo-new.png

logo-new.png

282 ms

contractors.jpg

contractors.jpg

699 ms

structural-steel-protection.jpg

structural-steel-protection.jpg

427 ms

concrete-masonry.jpg

concrete-masonry.jpg

427 ms

penetration-seals.jpg

penetration-seals.jpg

428 ms

ventilation.jpg

ventilation.jpg

429 ms

fire-rated-windows.jpg

fire-rated-windows.jpg

468 ms

cable-ducts.jpg

cable-ducts.jpg

891 ms

fire-dampers.jpg

fire-dampers.jpg

892 ms

fire-rated-walls.jpg

fire-rated-walls.jpg

661 ms

fire-rated-access-hatches.jpg

fire-rated-access-hatches.jpg

661 ms

fire-rated-partitions.jpg

fire-rated-partitions.jpg

700 ms

banner-home.jpg

banner-home.jpg

1351 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

19 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo.woff

24 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo.woff

58 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

980 ms

analytics.js

analytics.js

36 ms

collect

collect

13 ms

js

js

48 ms

Accessibility Review

fyreguard.com accessibility score

89

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

fyreguard.com best practices score

75

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

Page has valid source maps

SEO Factors

fyreguard.com SEO score

90

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

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

High

Tap targets are not sized appropriately

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

fyreguard.com

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