Tools & Wizards About Us
phoenixsafetyrail.com.au screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% 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

  • 86

    SEO

    Google-friendlier than
    60% of websites

phoenixsafetyrail.com.au

Balustrades & Screens | Melbourne, VIC | Phoenix Safety Rail

Page Load Speed

1.1 sec in total

First Response

36 ms

Resources Loaded

386 ms

Page Rendered

654 ms

phoenixsafetyrail.com.au screenshot

About Website

Visit phoenixsafetyrail.com.au now to see the best up-to-date Phoenix Safety Rail content and also check out these interesting facts you probably never knew about phoenixsafetyrail.com.au

Phoenix Safety Rail provides balustrades, pool fencing installation, shower screens & security doors. Servicing Melbourne and Surrounds. Call on 1300 361 328.

Visit phoenixsafetyrail.com.au

Key Findings

We analyzed Phoenixsafetyrail.com.au page load time and found that the first response time was 36 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

phoenixsafetyrail.com.au performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.062

97/100

15%

TTI (Time to Interactive)

Value7.5 s

48/100

10%

Network Requests Diagram

phoenixsafetyrail.com.au

36 ms

www.phoenixsafetyrail.com.au

79 ms

Phoenix+Logo-1920w.jpg

120 ms

jquery-3.7.0.min.js

30 ms

d-js-one-runtime-unified-desktop.min.js

46 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 15% of them (2 requests) were addressed to the original Phoenixsafetyrail.com.au, 38% (5 requests) were made to Static.cdn-website.com and 38% (5 requests) were made to Lirp.cdn-website.com. The less responsive or slowest element that took the longest time to load (165 ms) relates to the external source Lirp.cdn-website.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.9 kB (5%)

Content Size

203.7 kB

After Optimization

193.8 kB

  • Images
  • JavaScript

In fact, the total size of Phoenixsafetyrail.com.au main page is 203.7 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. Javascripts take 137.5 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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. This web page is already compressed.

Image Optimization

-15%

Potential reduce by 9.8 kB

  • Original 66.2 kB
  • After minification 56.4 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. Obviously, Phoenix Safety Rail needs image optimization as it can save up to 9.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 113 B

  • Original 137.5 kB
  • After minification 137.5 kB
  • After compression 137.4 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.

Requests Breakdown

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

Requests Now

9

After Optimization

6

  • Images
  • JavaScript

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

Network Requests Diagram

phoenixsafetyrail.com.au

phoenixsafetyrail.com.au

36 ms

www.phoenixsafetyrail.com.au

www.phoenixsafetyrail.com.au

79 ms

Phoenix+Logo-1920w.jpg

Phoenix+Logo-1920w.jpg

120 ms

jquery-3.7.0.min.js

jquery-3.7.0.min.js

30 ms

d-js-one-runtime-unified-desktop.min.js

d-js-one-runtime-unified-desktop.min.js

46 ms

d-js-jquery-migrate.min.js

d-js-jquery-migrate.min.js

44 ms

dxmscript.min.js

dxmscript.min.js

163 ms

Phoenix+Logo+with+white+text-b0be1980-480w.png

Phoenix+Logo+with+white+text-b0be1980-480w.png

113 ms

GettyImages-502447535-1920w.jpg

GettyImages-502447535-1920w.jpg

165 ms

whitebg1-1920w.png

whitebg1-1920w.png

86 ms

transparent_500x500-1404w.png

transparent_500x500-1404w.png

159 ms

dm-font.woff

dm-font.woff

14 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

4 ms

Accessibility Review

phoenixsafetyrail.com.au 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.

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

phoenixsafetyrail.com.au 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

phoenixsafetyrail.com.au SEO score

86

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phoenixsafetyrail.com.au can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Phoenixsafetyrail.com.au main page’s claimed encoding is . 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

phoenixsafetyrail.com.au

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