Tools & Wizards About Us
burnco.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

burnco.com

Building Foundations For A Stronger Future - BURNCO

Page Load Speed

3.5 sec in total

First Response

133 ms

Resources Loaded

2.7 sec

Page Rendered

740 ms

burnco.com screenshot

About Website

Welcome to burnco.com homepage info - get ready to check BURNCO best content for Canada right away, or after learning these important things about burnco.com

As a leader in building materials, BURNCO provides the broadest range of aggregate, ready mix, and asphalt products that meet your specific requirements with uncompromising quality and a customer-firs...

Visit burnco.com

Key Findings

We analyzed Burnco.com page load time and found that the first response time was 133 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

burnco.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.243

51/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

burnco.com

133 ms

www.burnco.com

1019 ms

wpa.css

119 ms

search-filter.min.css

181 ms

style.min.css

192 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 70% of them (75 requests) were addressed to the original Burnco.com, 8% (9 requests) were made to Cdnjs.cloudflare.com and 7% (8 requests) were made to Burnco-web-wordpress-prod.s3.us-west-2.amazonaws.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Burnco.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 296.1 kB (42%)

Content Size

698.9 kB

After Optimization

402.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Burnco.com main page is 698.9 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. 70% of websites need less resources to load. Javascripts take 255.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 206.6 kB

  • Original 240.8 kB
  • After minification 234.2 kB
  • After compression 34.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. 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 206.6 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 184 B

  • Original 100.3 kB
  • After minification 100.1 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. BURNCO images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 66.8 kB

  • Original 255.1 kB
  • After minification 255.1 kB
  • After compression 188.3 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 66.8 kB or 26% of the original size.

CSS Optimization

-22%

Potential reduce by 22.5 kB

  • Original 102.8 kB
  • After minification 102.8 kB
  • After compression 80.3 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. Burnco.com needs all CSS files to be minified and compressed as it can save up to 22.5 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (87%)

Requests Now

83

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

burnco.com

burnco.com

133 ms

www.burnco.com

www.burnco.com

1019 ms

wpa.css

wpa.css

119 ms

search-filter.min.css

search-filter.min.css

181 ms

style.min.css

style.min.css

192 ms

theme.min.css

theme.min.css

194 ms

header-footer.min.css

header-footer.min.css

196 ms

frontend-lite.min.css

frontend-lite.min.css

262 ms

post-5.css

post-5.css

196 ms

style.basic.css

style.basic.css

242 ms

style-curvy-black.css

style-curvy-black.css

256 ms

elementor-icons.min.css

elementor-icons.min.css

258 ms

swiper.min.css

swiper.min.css

268 ms

frontend-lite.min.css

frontend-lite.min.css

270 ms

global.css

global.css

304 ms

post-9110.css

post-9110.css

319 ms

post-12.css

post-12.css

323 ms

post-118.css

post-118.css

325 ms

all.min.css

all.min.css

57 ms

slick.min.css

slick.min.css

70 ms

slick-theme.min.css

slick-theme.min.css

67 ms

main.css

main.css

326 ms

css

css

65 ms

fontawesome.min.css

fontawesome.min.css

390 ms

solid.min.css

solid.min.css

362 ms

regular.min.css

regular.min.css

381 ms

brands.min.css

brands.min.css

384 ms

script.min.js

script.min.js

389 ms

jquery.min.js

jquery.min.js

454 ms

jquery-migrate.min.js

jquery-migrate.min.js

422 ms

gsap.min.js

gsap.min.js

61 ms

splitting.min.js

splitting.min.js

444 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

64 ms

slick.min.js

slick.min.js

66 ms

main.js

main.js

448 ms

js

js

80 ms

css

css

73 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

452 ms

animations.min.css

animations.min.css

449 ms

wpa.js

wpa.js

478 ms

hello-frontend.min.js

hello-frontend.min.js

504 ms

asl-prereq.js

asl-prereq.js

465 ms

asl-core.js

asl-core.js

472 ms

asl-results-vertical.js

asl-results-vertical.js

472 ms

asl-load.js

asl-load.js

471 ms

asl-wrapper.js

asl-wrapper.js

497 ms

wpmssab.min.js

wpmssab.min.js

523 ms

SmoothScroll.min.js

SmoothScroll.min.js

468 ms

wpmss.min.js

wpmss.min.js

410 ms

new-tab.js

new-tab.js

402 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

400 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

420 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

448 ms

webpack.runtime.min.js

webpack.runtime.min.js

407 ms

frontend-modules.min.js

frontend-modules.min.js

404 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

399 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

390 ms

wp-polyfill.min.js

wp-polyfill.min.js

409 ms

hooks.min.js

hooks.min.js

438 ms

i18n.min.js

i18n.min.js

411 ms

frontend.min.js

frontend.min.js

408 ms

waypoints.min.js

waypoints.min.js

407 ms

fonts.css

fonts.css

402 ms

navigation.css

navigation.css

413 ms

buttons.css

buttons.css

408 ms

transitions.css

transitions.css

397 ms

template_modules.css

template_modules.css

409 ms

custom_elementor_modules.css

custom_elementor_modules.css

408 ms

carousels.css

carousels.css

400 ms

forms.css

forms.css

375 ms

core.min.js

core.min.js

534 ms

frontend.min.js

frontend.min.js

531 ms

elements-handlers.min.js

elements-handlers.min.js

527 ms

underscore.min.js

underscore.min.js

528 ms

wp-util.min.js

wp-util.min.js

527 ms

frontend.min.js

frontend.min.js

499 ms

bg-homepage-hero-mobile.webp

bg-homepage-hero-mobile.webp

623 ms

background-dotted-mask.png

background-dotted-mask.png

234 ms

background-topography-mask-light.png

background-topography-mask-light.png

282 ms

background-topography-mask-red.png

background-topography-mask-red.png

235 ms

bg-building-our-future.webp

bg-building-our-future.webp

130 ms

burnco-sustaintainable-video-fallback.webp

burnco-sustaintainable-video-fallback.webp

130 ms

thumb-recycled-asphalt-page-1024x.webp

thumb-recycled-asphalt-page-1024x.webp

130 ms

thumb-ready-mix-page-1024x.webp

thumb-ready-mix-page-1024x.webp

130 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

57 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

89 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

135 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

153 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

152 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

153 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

152 ms

ArupalaGroteskTrial-Ultra.ttf

ArupalaGroteskTrial-Ultra.ttf

406 ms

ArupalaGroteskTrial-SuperBold.ttf

ArupalaGroteskTrial-SuperBold.ttf

455 ms

ArupalaGroteskTrial-Bold.ttf

ArupalaGroteskTrial-Bold.ttf

472 ms

AndersonGrotesk-Bold.otf

AndersonGrotesk-Bold.otf

471 ms

AndersonGrotesk-Ultrabold.otf

AndersonGrotesk-Ultrabold.otf

471 ms

AndersonGrotesk-Black.otf

AndersonGrotesk-Black.otf

502 ms

AndersonGrotesk.otf

AndersonGrotesk.otf

502 ms

AndersonGrotesk-Light.otf

AndersonGrotesk-Light.otf

534 ms

fa-solid-900.ttf

fa-solid-900.ttf

53 ms

fa-regular-400.ttf

fa-regular-400.ttf

37 ms

eicons.woff

eicons.woff

288 ms

fa-brands-400.woff

fa-brands-400.woff

264 ms

fa-brands-400.ttf

fa-brands-400.ttf

52 ms

fa-solid-900.woff

fa-solid-900.woff

237 ms

fa-regular-400.woff

fa-regular-400.woff

194 ms

burnco-logo.png

burnco-logo.png

203 ms

Accessibility Review

burnco.com accessibility score

87

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

burnco.com best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

burnco.com SEO score

85

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

Links do not have descriptive text

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

burnco.com

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