Tools & Wizards About Us
fireworld.com.au screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fireworld.com.au

Fireworld - Fire Extinguishers, Fire Blankets, Hoses & Accessories

Page Load Speed

5.8 sec in total

First Response

1.1 sec

Resources Loaded

4.6 sec

Page Rendered

193 ms

fireworld.com.au screenshot

About Website

Click here to check amazing Fireworld content. Otherwise, check out these important facts you probably never knew about fireworld.com.au

Fireworld fire extinguishers, fire blankets, fire hoses, vehicle brackets and other fire protection products.

Visit fireworld.com.au

Key Findings

We analyzed Fireworld.com.au page load time and found that the first response time was 1.1 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

fireworld.com.au performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

fireworld.com.au

1086 ms

js

66 ms

jquery-3.1.0.min.js

441 ms

magnific-popup.css

655 ms

maximenuckmobile.css

657 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 79% of them (27 requests) were addressed to the original Fireworld.com.au, 12% (4 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fireworld.com.au.

Page Optimization Overview & Recommendations

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

Content Size

366.2 kB

After Optimization

334.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fireworld.com.au main page is 366.2 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. Images take 241.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 21.7 kB

  • Original 26.7 kB
  • After minification 24.9 kB
  • After compression 5.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 21.7 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 1.5 kB

  • Original 241.7 kB
  • After minification 240.2 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. Fireworld images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 2.4 kB

  • Original 77.9 kB
  • After minification 77.9 kB
  • After compression 75.5 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

-30%

Potential reduce by 5.9 kB

  • Original 19.8 kB
  • After minification 19.8 kB
  • After compression 13.9 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. Fireworld.com.au needs all CSS files to be minified and compressed as it can save up to 5.9 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (71%)

Requests Now

28

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fireworld. 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 from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fireworld.com.au

fireworld.com.au

1086 ms

js

js

66 ms

jquery-3.1.0.min.js

jquery-3.1.0.min.js

441 ms

magnific-popup.css

magnific-popup.css

655 ms

maximenuckmobile.css

maximenuckmobile.css

657 ms

jcemediabox.css

jcemediabox.css

659 ms

style.css

style.css

657 ms

system.css

system.css

659 ms

general.css

general.css

681 ms

maximenuck_maximenuck96.css

maximenuck_maximenuck96.css

872 ms

maximenuresponsiveck.css

maximenuresponsiveck.css

873 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

875 ms

k2.frontend.js

k2.frontend.js

875 ms

jquery-noconflict.js

jquery-noconflict.js

874 ms

jquery-migrate.min.js

jquery-migrate.min.js

904 ms

maximenuckmobile.js

maximenuckmobile.js

1089 ms

jcemediabox.js

jcemediabox.js

1308 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

1094 ms

maximenuck.js

maximenuck.js

1091 ms

css

css

35 ms

css

css

80 ms

template.css

template.css

1092 ms

system.css

system.css

469 ms

logo_fireworld.png

logo_fireworld.png

221 ms

transparent.gif

transparent.gif

248 ms

icon_search.png

icon_search.png

221 ms

header_bg_homepage.jpg

header_bg_homepage.jpg

1295 ms

fireworld_logo_small.png

fireworld_logo_small.png

220 ms

popup.html

popup.html

219 ms

tooltip.html

tooltip.html

412 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

39 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

43 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

53 ms

FwZY7-Qmy14u9lezJ-6H6Mw.ttf

FwZY7-Qmy14u9lezJ-6H6Mw.ttf

60 ms

Accessibility Review

fireworld.com.au accessibility score

100

Accessibility Issues

Best Practices

fireworld.com.au best practices score

67

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

Browser errors were logged to the console

SEO Factors

fireworld.com.au SEO score

92

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

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 Fireworld.com.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 Fireworld.com.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

fireworld.com.au

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: