Tools & Wizards About Us
proflamefireplaces.ca screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

proflamefireplaces.ca

Gas Fireplace Repair, Cleaning, Replacement Edmonton area.

Page Load Speed

38.4 sec in total

First Response

1.2 sec

Resources Loaded

36.9 sec

Page Rendered

187 ms

proflamefireplaces.ca screenshot

About Website

Visit proflamefireplaces.ca now to see the best up-to-date Proflame Fireplace S content and also check out these interesting facts you probably never knew about proflamefireplaces.ca

Pro-Flame Fireplace Services has been servicing gas fireplaces in the Edmonton and surrounding area since 1994.

Visit proflamefireplaces.ca

Key Findings

We analyzed Proflamefireplaces.ca page load time and found that the first response time was 1.2 sec and then it took 37.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

proflamefireplaces.ca performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.7 s

35/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

proflamefireplaces.ca

1237 ms

www.proflamefireplaces.ca

474 ms

bootstrap.min.css

65 ms

freelancer.css

1656 ms

font-awesome.min.css

2089 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 69% of them (20 requests) were addressed to the original Proflamefireplaces.ca, 7% (2 requests) were made to Fonts.googleapis.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Proflamefireplaces.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.9 kB (20%)

Content Size

29.1 kB

After Optimization

23.2 kB

  • HTML
  • JavaScript

In fact, the total size of Proflamefireplaces.ca main page is 29.1 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 21.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 5.9 kB

  • Original 8.1 kB
  • After minification 5.8 kB
  • After compression 2.2 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 2.3 kB, which is 29% 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 5.9 kB or 72% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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 11 (61%)

Requests Now

18

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proflamefireplaces.ca

proflamefireplaces.ca

1237 ms

www.proflamefireplaces.ca

www.proflamefireplaces.ca

474 ms

bootstrap.min.css

bootstrap.min.css

65 ms

freelancer.css

freelancer.css

1656 ms

font-awesome.min.css

font-awesome.min.css

2089 ms

css

css

41 ms

css

css

60 ms

jquery.min.js

jquery.min.js

14987 ms

bootstrap.min.js

bootstrap.min.js

6705 ms

jquery.easing.min.js

jquery.easing.min.js

32 ms

jqBootstrapValidation.js

jqBootstrapValidation.js

8219 ms

contact_me.js

contact_me.js

9023 ms

freelancer.js

freelancer.js

9590 ms

addthis_widget.js

addthis_widget.js

25 ms

analytics.js

analytics.js

51 ms

PhotoGray_browser_bg-2.jpg

PhotoGray_browser_bg-2.jpg

8447 ms

Darkroom_spotlight.jpg

Darkroom_spotlight.jpg

11076 ms

shapeimage_1.png

shapeimage_1.png

12907 ms

PhotoGray_nav_bg.png

PhotoGray_nav_bg.png

16877 ms

first_new.jpg

first_new.jpg

20116 ms

second_new.jpg

second_new.jpg

20117 ms

third_new.jpg

third_new.jpg

20117 ms

fourth_new.jpg

fourth_new.jpg

20117 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

34 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

39 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

20080 ms

collect

collect

16 ms

js

js

67 ms

glyphicons-halflings-regular.ttf

glyphicons-halflings-regular.ttf

13002 ms

Accessibility Review

proflamefireplaces.ca accessibility score

86

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

ARIA input fields do not have accessible names

High

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

Best Practices

proflamefireplaces.ca 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

proflamefireplaces.ca SEO score

100

Search Engine Optimization Advices

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 Proflamefireplaces.ca 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 Proflamefireplaces.ca 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

proflamefireplaces.ca

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