Tools & Wizards About Us
guardianfire.com screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

guardianfire.com

Guardian Fire Equipment, Inc. - Manufacturer and Supplier of Quality Fire Fighting Equipment

Page Load Speed

856 ms in total

First Response

121 ms

Resources Loaded

667 ms

Page Rendered

68 ms

guardianfire.com screenshot

About Website

Visit guardianfire.com now to see the best up-to-date Guardian Fire content for United States and also check out these interesting facts you probably never knew about guardianfire.com

Manufacturer and supplier of fire equipment; including fire cabinets, fire dept valves, fire extinguishers, storz connections, Siamese fire dept connections,fire monitors, monitor nozzles, fiberglass ...

Visit guardianfire.com

Key Findings

We analyzed Guardianfire.com page load time and found that the first response time was 121 ms and then it took 735 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

guardianfire.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

guardianfire.com

121 ms

guardianfire.com

143 ms

main.css

35 ms

prototype.js

133 ms

effects.js

161 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 94% of them (34 requests) were addressed to the original Guardianfire.com, 3% (1 request) were made to Google-analytics.com and 3% (1 request) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (198 ms) belongs to the original domain Guardianfire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 250.9 kB (59%)

Content Size

425.0 kB

After Optimization

174.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Guardianfire.com main page is 425.0 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. 20% of websites need less resources to load. Javascripts take 278.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 11.2 kB

  • Original 14.6 kB
  • After minification 13.6 kB
  • After compression 3.4 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 11.2 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 2.4 kB

  • Original 114.1 kB
  • After minification 111.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. Guardian Fire images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 222.4 kB

  • Original 278.2 kB
  • After minification 210.7 kB
  • After compression 55.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 222.4 kB or 80% of the original size.

CSS Optimization

-82%

Potential reduce by 14.9 kB

  • Original 18.2 kB
  • After minification 12.7 kB
  • After compression 3.3 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. Guardianfire.com needs all CSS files to be minified and compressed as it can save up to 14.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (32%)

Requests Now

34

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

guardianfire.com

guardianfire.com

121 ms

guardianfire.com

guardianfire.com

143 ms

main.css

main.css

35 ms

prototype.js

prototype.js

133 ms

effects.js

effects.js

161 ms

common_functions.js

common_functions.js

141 ms

lightwindow.css

lightwindow.css

141 ms

lightwindow.js

lightwindow.js

198 ms

tinyaccordion_script.js

tinyaccordion_script.js

142 ms

urchin.js

urchin.js

6 ms

searchbox_bg.gif

searchbox_bg.gif

34 ms

__utm.gif

__utm.gif

15 ms

main_content_bg.gif

main_content_bg.gif

33 ms

menuTile.jpg

menuTile.jpg

32 ms

menuLogo.jpg

menuLogo.jpg

34 ms

menuTitle.jpg

menuTitle.jpg

65 ms

nav_products.png

nav_products.png

35 ms

nav_datasheets.png

nav_datasheets.png

34 ms

nav_contact.png

nav_contact.png

64 ms

nav_pricelist.png

nav_pricelist.png

65 ms

nav_estimator.png

nav_estimator.png

65 ms

nav_shopping.png

nav_shopping.png

65 ms

nav_search.png

nav_search.png

66 ms

arrow_red_square.gif

arrow_red_square.gif

96 ms

header_shadow.jpg

header_shadow.jpg

97 ms

miami_skyline.jpg

miami_skyline.jpg

130 ms

nojs_background.gif

nojs_background.gif

96 ms

sidebar_right_tile.gif

sidebar_right_tile.gif

97 ms

feature_productapplications_off.gif

feature_productapplications_off.gif

98 ms

feature_newproducts_off.gif

feature_newproducts_off.gif

127 ms

feature_businesspartners_off.gif

feature_businesspartners_off.gif

128 ms

focus_shoppingcart_off.gif

focus_shoppingcart_off.gif

128 ms

focus_jobestimator_off.gif

focus_jobestimator_off.gif

129 ms

focus_distributors_off.gif

focus_distributors_off.gif

130 ms

footer_cap.jpg

footer_cap.jpg

159 ms

black.png

black.png

33 ms

Accessibility Review

guardianfire.com accessibility score

67

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

guardianfire.com best practices score

58

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

guardianfire.com SEO score

54

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guardianfire.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 Guardianfire.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

guardianfire.com

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