Tools & Wizards About Us
firepro.net.au screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

firepro.net.au

FirePro Condensed Aerosol - Reinventing Fire Suppression

Page Load Speed

8.5 sec in total

First Response

469 ms

Resources Loaded

7.7 sec

Page Rendered

282 ms

firepro.net.au screenshot

About Website

Welcome to firepro.net.au homepage info - get ready to check Fire Pro best content for Australia right away, or after learning these important things about firepro.net.au

FirePro Aerosol fire suppression generators are highly effective, compact, low maintenance and cost effective. Suitable for all finds of Fire risk.

Visit firepro.net.au

Key Findings

We analyzed Firepro.net.au page load time and found that the first response time was 469 ms and then it took 8 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

firepro.net.au performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value20.2 s

0/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

firepro.net.au

469 ms

firepro.au

4102 ms

pdfg-front.css

218 ms

swpm.common.css

436 ms

style.css

1082 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Firepro.net.au, 53% (31 requests) were made to Firepro.au and 24% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Firepro.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 925.8 kB (29%)

Content Size

3.2 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Firepro.net.au main page is 3.2 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. 50% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 55.3 kB

  • Original 70.1 kB
  • After minification 69.3 kB
  • After compression 14.9 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 55.3 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 266.8 kB

  • Original 2.4 MB
  • After minification 2.1 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, Fire Pro needs image optimization as it can save up to 266.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 275.1 kB

  • Original 376.2 kB
  • After minification 354.7 kB
  • After compression 101.2 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 275.1 kB or 73% of the original size.

CSS Optimization

-76%

Potential reduce by 328.6 kB

  • Original 432.4 kB
  • After minification 391.3 kB
  • After compression 103.7 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. Firepro.net.au needs all CSS files to be minified and compressed as it can save up to 328.6 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (60%)

Requests Now

42

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

firepro.net.au

firepro.net.au

469 ms

firepro.au

firepro.au

4102 ms

pdfg-front.css

pdfg-front.css

218 ms

swpm.common.css

swpm.common.css

436 ms

style.css

style.css

1082 ms

dashicons.min.css

dashicons.min.css

1086 ms

genericons.css

genericons.css

875 ms

font-awesome.min.css

font-awesome.min.css

871 ms

all.min.css

all.min.css

875 ms

style.css

style.css

1101 ms

font-awesome.css

font-awesome.css

1089 ms

smartslider.min.css

smartslider.min.css

1091 ms

css

css

35 ms

jquery.min.js

jquery.min.js

1308 ms

jquery-migrate.min.js

jquery-migrate.min.js

1296 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

1298 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

1304 ms

jquery.theme-main.min.js

jquery.theme-main.min.js

1306 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

1329 ms

n2.min.js

n2.min.js

1515 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

1945 ms

ss-simple.min.js

ss-simple.min.js

1524 ms

w-arrow-image.min.js

w-arrow-image.min.js

1525 ms

w-bullet.min.js

w-bullet.min.js

1527 ms

so-css-vantage.css

so-css-vantage.css

1535 ms

pdfg.front.js

pdfg.front.js

1730 ms

hoverIntent.min.js

hoverIntent.min.js

1736 ms

maxmegamenu.js

maxmegamenu.js

1741 ms

public.js

public.js

1742 ms

apps_power.png

apps_power.png

1363 ms

fse8-1.png

fse8-1.png

441 ms

pfas_free.2.png

pfas_free.2.png

611 ms

slider_marine.png

slider_marine.png

1697 ms

slider_fp_product.png

slider_fp_product.png

1510 ms

apps_mining.png

apps_mining.png

1585 ms

apps_agriculture.png

apps_agriculture.png

1371 ms

apps_mobile.png

apps_mobile.png

1371 ms

apps_marine.png

apps_marine.png

1160 ms

firepro.png

firepro.png

1392 ms

apps_lithium.png

apps_lithium.png

1378 ms

apps_manufact.png

apps_manufact.png

1578 ms

apps_cabinets.png

apps_cabinets.png

1804 ms

apps_bus.png

apps_bus.png

1807 ms

apps_rail.png

apps_rail.png

1811 ms

wARDj0u

wARDj0u

7 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

40 ms

KFOmCnqEu92Fr1Mu7GxMOzY.woff

KFOmCnqEu92Fr1Mu7GxMOzY.woff

43 ms

KFOmCnqEu92Fr1Mu7WxMOzY.woff

KFOmCnqEu92Fr1Mu7WxMOzY.woff

29 ms

KFOmCnqEu92Fr1Mu4WxMOzY.woff

KFOmCnqEu92Fr1Mu4WxMOzY.woff

29 ms

KFOmCnqEu92Fr1Mu7mxMOzY.woff

KFOmCnqEu92Fr1Mu7mxMOzY.woff

39 ms

KFOmCnqEu92Fr1Mu5mxMOzY.woff

KFOmCnqEu92Fr1Mu5mxMOzY.woff

40 ms

KFOmCnqEu92Fr1Mu72xMOzY.woff

KFOmCnqEu92Fr1Mu72xMOzY.woff

43 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

40 ms

KFOlCnqEu92Fr1MmSU5fChc-EsA.woff

KFOlCnqEu92Fr1MmSU5fChc-EsA.woff

43 ms

KFOlCnqEu92Fr1MmSU5fCxc-EsA.woff

KFOlCnqEu92Fr1MmSU5fCxc-EsA.woff

43 ms

KFOlCnqEu92Fr1MmSU5fBxc-EsA.woff

KFOlCnqEu92Fr1MmSU5fBxc-EsA.woff

45 ms

KFOlCnqEu92Fr1MmSU5fCBc-EsA.woff

KFOlCnqEu92Fr1MmSU5fCBc-EsA.woff

43 ms

KFOlCnqEu92Fr1MmSU5fABc-EsA.woff

KFOlCnqEu92Fr1MmSU5fABc-EsA.woff

45 ms

KFOlCnqEu92Fr1MmSU5fCRc-EsA.woff

KFOlCnqEu92Fr1MmSU5fCRc-EsA.woff

45 ms

Accessibility Review

firepro.net.au accessibility score

89

Accessibility Issues

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

firepro.net.au 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

firepro.net.au SEO score

91

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

Image elements do not have [alt] attributes

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 Firepro.net.au 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 Firepro.net.au 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

firepro.net.au

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