Tools & Wizards About Us
regency-fire.com.au screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

regency-fire.com.au

Regency Fireplace Products | Gas Fireplaces & Wood Heaters

Page Load Speed

2.9 sec in total

First Response

168 ms

Resources Loaded

2.3 sec

Page Rendered

480 ms

regency-fire.com.au screenshot

About Website

Welcome to regency-fire.com.au homepage info - get ready to check Regency Fire best content for Australia right away, or after learning these important things about regency-fire.com.au

Proudly Made in Canada for over 40 years, Regency is known worldwide for our attention to detail, heat, efficiency, safety and unmatched quality. At Regency, it's more than a fireplace…

Visit regency-fire.com.au

Key Findings

We analyzed Regency-fire.com.au page load time and found that the first response time was 168 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

regency-fire.com.au performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value2,540 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.259

48/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

regency-fire.com.au

168 ms

regency-fire.com.au

421 ms

bgb7kap.css

67 ms

jquery-3.3.1.min.js

177 ms

GetResource.ashx

249 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 59% of them (57 requests) were addressed to the original Regency-fire.com.au, 26% (25 requests) were made to Embedsocial.com and 4% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (854 ms) belongs to the original domain Regency-fire.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.2 kB (8%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Regency-fire.com.au main page is 2.0 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 75.3 kB

  • Original 96.6 kB
  • After minification 85.6 kB
  • After compression 21.3 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. This page needs HTML code to be minified as it can gain 10.9 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 75.3 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 8.8 kB

  • Original 1.5 MB
  • After minification 1.5 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. Regency Fire images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 64.6 kB

  • Original 381.2 kB
  • After minification 380.7 kB
  • After compression 316.6 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 64.6 kB or 17% of the original size.

CSS Optimization

-14%

Potential reduce by 2.5 kB

  • Original 17.4 kB
  • After minification 17.1 kB
  • After compression 15.0 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. Regency-fire.com.au needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 14% of the original size.

Requests Breakdown

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

Requests Now

78

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

regency-fire.com.au

regency-fire.com.au

168 ms

regency-fire.com.au

regency-fire.com.au

421 ms

bgb7kap.css

bgb7kap.css

67 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

177 ms

GetResource.ashx

GetResource.ashx

249 ms

fancybox.css

fancybox.css

39 ms

GetResource.ashx

GetResource.ashx

352 ms

GetResource.ashx

GetResource.ashx

435 ms

swiper-bundle.min.css

swiper-bundle.min.css

53 ms

GetCSS.aspx

GetCSS.aspx

441 ms

all.css

all.css

46 ms

bootstrap-icons.css

bootstrap-icons.css

58 ms

WebResource.axd

WebResource.axd

352 ms

ScriptResource.axd

ScriptResource.axd

351 ms

ScriptResource.axd

ScriptResource.axd

432 ms

ScriptResource.axd

ScriptResource.axd

431 ms

swiper-bundle.min.css

swiper-bundle.min.css

30 ms

p.css

p.css

29 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

355 ms

GetResource.ashx

GetResource.ashx

378 ms

GetResource.ashx

GetResource.ashx

438 ms

js

js

74 ms

popper.min.js

popper.min.js

441 ms

bootstrap.min.js

bootstrap.min.js

440 ms

swiper.min.js

swiper.min.js

453 ms

fancybox.umd.js

fancybox.umd.js

17 ms

webfont.js

webfont.js

23 ms

footer.js

footer.js

451 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

452 ms

gtm.js

gtm.js

66 ms

2024-Electric-Promo-WB-1920-x-680.jpg

2024-Electric-Promo-WB-1920-x-680.jpg

382 ms

Logo_Regency_Red.svg

Logo_Regency_Red.svg

148 ms

2021-home-icon.svg

2021-home-icon.svg

151 ms

2021-regency-map-icon.svg

2021-regency-map-icon.svg

149 ms

2021-regency-flames.svg

2021-regency-flames.svg

151 ms

blueprint-temp.aspx

blueprint-temp.aspx

153 ms

cad-temp.aspx

cad-temp.aspx

153 ms

contact-temp.aspx

contact-temp.aspx

224 ms

regencyIconWhite.svg

regencyIconWhite.svg

226 ms

fire.png

fire.png

228 ms

gas.png

gas.png

228 ms

electric.png

electric.png

231 ms

Regency-Onyx-EX150-A-400x225.aspx

Regency-Onyx-EX150-A-400x225.aspx

230 ms

Cardinia-A-400x225.aspx

Cardinia-A-400x225.aspx

312 ms

Bellerieve-A-400x225.aspx

Bellerieve-A-400x225.aspx

312 ms

facebook.aspx

facebook.aspx

313 ms

twitter.aspx

twitter.aspx

314 ms

pinterest.aspx

pinterest.aspx

314 ms

instagram.aspx

instagram.aspx

316 ms

NIBE_CMYK.svg

NIBE_CMYK.svg

383 ms

d

d

4 ms

d

d

20 ms

d

d

21 ms

ht.js

ht.js

72 ms

icon-facebook.png

icon-facebook.png

828 ms

icon-youtube.png

icon-youtube.png

326 ms

icon-instagram.png

icon-instagram.png

326 ms

icon-pinterest.png

icon-pinterest.png

329 ms

icon-twitter.png

icon-twitter.png

330 ms

icon-houzz.png

icon-houzz.png

402 ms

2024-Electric-Promo-WB-1920-x-680.jpg

2024-Electric-Promo-WB-1920-x-680.jpg

346 ms

iframe.js

iframe.js

4 ms

iframe-lightbox.min.css

iframe-lightbox.min.css

8 ms

universal-popup.js

universal-popup.js

9 ms

universal-popup.css

universal-popup.css

9 ms

238 ms

blueprint-temp.aspx

blueprint-temp.aspx

313 ms

cad-temp.aspx

cad-temp.aspx

336 ms

contact-temp.aspx

contact-temp.aspx

267 ms

Regency-Onyx-EX150-A-400x225.aspx

Regency-Onyx-EX150-A-400x225.aspx

319 ms

stylesheet.css

stylesheet.css

5 ms

js

js

35 ms

image_0.jpeg

image_0.jpeg

124 ms

image_0.jpeg

image_0.jpeg

231 ms

image_0.jpeg

image_0.jpeg

172 ms

Roboto-Regular.woff

Roboto-Regular.woff

12 ms

Roboto-Bold.woff

Roboto-Bold.woff

14 ms

Cardinia-A-400x225.aspx

Cardinia-A-400x225.aspx

350 ms

Bellerieve-A-400x225.aspx

Bellerieve-A-400x225.aspx

363 ms

facebook.aspx

facebook.aspx

282 ms

twitter.aspx

twitter.aspx

282 ms

pinterest.aspx

pinterest.aspx

341 ms

instagram.aspx

instagram.aspx

351 ms

iframeContent.min.js

iframeContent.min.js

5 ms

image_0.jpeg

image_0.jpeg

157 ms

image_0.jpeg

image_0.jpeg

148 ms

image_0.jpeg

image_0.jpeg

218 ms

image_0.jpeg

image_0.jpeg

196 ms

image_0.jpeg

image_0.jpeg

353 ms

image_0.jpeg

image_0.jpeg

354 ms

image_0.jpeg

image_0.jpeg

263 ms

image_0.jpeg

image_0.jpeg

367 ms

image_0.jpeg

image_0.jpeg

354 ms

image_0.jpeg

image_0.jpeg

397 ms

image_0.jpeg

image_0.jpeg

433 ms

image_0.jpeg

image_0.jpeg

522 ms

2024-Electric-Promo-WB-1920-x-680.jpg

2024-Electric-Promo-WB-1920-x-680.jpg

854 ms

Accessibility Review

regency-fire.com.au accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

regency-fire.com.au best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

regency-fire.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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regency-fire.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 Regency-fire.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

regency-fire.com.au

Open Graph data is detected on the main page of Regency Fire. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: