Tools & Wizards About Us
billingcentre.purolator.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

billingcentre.purolator.com

Shipping, Freight & Courier Solutions | Purolator

Page Load Speed

2.6 sec in total

First Response

149 ms

Resources Loaded

1.3 sec

Page Rendered

1.1 sec

billingcentre.purolator.com screenshot

About Website

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

From integrated business solutions to mailing and tracking services, Canadians rely on Canada's largest courier network for all their shipping needs.

Visit billingcentre.purolator.com

Key Findings

We analyzed Billingcentre.purolator.com page load time and found that the first response time was 149 ms and then it took 2.4 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

billingcentre.purolator.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value2,420 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

billingcentre.purolator.com

149 ms

billingcentre.purolator.com

114 ms

home.page

148 ms

en

70 ms

css_Cxgi_TP7mjeSCz24mSSDJI1DfzI9J9kJsnFZD74_GIM.css

48 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Billingcentre.purolator.com, 92% (86 requests) were made to Purolator.com and 2% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (430 ms) relates to the external source Purolator.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.1 kB (3%)

Content Size

5.0 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Billingcentre.purolator.com main page is 5.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. 45% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 130.8 kB

  • Original 165.1 kB
  • After minification 147.1 kB
  • After compression 34.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 18.0 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 130.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 92 B

  • Original 4.6 MB
  • After minification 4.6 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. Billingcentre Purolator images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 6.0 kB

  • Original 152.6 kB
  • After minification 152.4 kB
  • After compression 146.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 153 B

  • Original 55.7 kB
  • After minification 55.7 kB
  • After compression 55.5 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. Billingcentre.purolator.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

83

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

billingcentre.purolator.com

billingcentre.purolator.com

149 ms

billingcentre.purolator.com

billingcentre.purolator.com

114 ms

home.page

home.page

148 ms

en

en

70 ms

css_Cxgi_TP7mjeSCz24mSSDJI1DfzI9J9kJsnFZD74_GIM.css

css_Cxgi_TP7mjeSCz24mSSDJI1DfzI9J9kJsnFZD74_GIM.css

48 ms

css_VZrXTA6bKJQUrrjIJrT66KvRa4x4UzxHVwwNdbs9-Wo.css

css_VZrXTA6bKJQUrrjIJrT66KvRa4x4UzxHVwwNdbs9-Wo.css

54 ms

autopilot_sdk.js

autopilot_sdk.js

50 ms

jquery.min.js

jquery.min.js

114 ms

once.min.js

once.min.js

111 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

112 ms

drupal.js

drupal.js

124 ms

drupal.init.js

drupal.init.js

126 ms

debounce.js

debounce.js

125 ms

dblazy.min.js

dblazy.min.js

127 ms

blazy.once.min.js

blazy.once.min.js

130 ms

blazy.sanitizer.min.js

blazy.sanitizer.min.js

131 ms

blazy.dom.min.js

blazy.dom.min.js

132 ms

blazy.base.min.js

blazy.base.min.js

133 ms

blazy.dataset.min.js

blazy.dataset.min.js

135 ms

blazy.viewport.min.js

blazy.viewport.min.js

149 ms

blazy.xlazy.min.js

blazy.xlazy.min.js

145 ms

blazy.observer.min.js

blazy.observer.min.js

232 ms

blazy.min.js

blazy.min.js

170 ms

bio.min.js

bio.min.js

168 ms

bio.media.min.js

bio.media.min.js

179 ms

blazy.drupal.min.js

blazy.drupal.min.js

191 ms

blazy.compat.min.js

blazy.compat.min.js

191 ms

index.umd.min.js

index.umd.min.js

214 ms

popper-utils.min.js

popper-utils.min.js

206 ms

popper.min.js

popper.min.js

218 ms

jquery.validate.min.js

jquery.validate.min.js

23 ms

bootstrap.min.js

bootstrap.min.js

230 ms

stacktable.js

stacktable.js

231 ms

purolator_theme.script.js

purolator_theme.script.js

357 ms

stickybits.min.js

stickybits.min.js

358 ms

gtm.js

gtm.js

358 ms

gtag.js

gtag.js

359 ms

progress.js

progress.js

360 ms

loadjs.min.js

loadjs.min.js

364 ms

announce.js

announce.js

360 ms

message.js

message.js

360 ms

object-assign-auto.min.js

object-assign-auto.min.js

28 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

107 ms

ajax.js

ajax.js

360 ms

gtag.ajax.js

gtag.ajax.js

322 ms

FSR-Certified_0.png

FSR-Certified_0.png

49 ms

back_to_top.js

back_to_top.js

259 ms

cv.jquery.validate.js

cv.jquery.validate.js

258 ms

chosen.jquery.min.js

chosen.jquery.min.js

258 ms

chosen.js

chosen.js

245 ms

states.js

states.js

249 ms

modal.js

modal.js

249 ms

blazy_bg_init.js

blazy_bg_init.js

247 ms

search_header.js

search_header.js

264 ms

chatbot.js

chatbot.js

271 ms

ssm.min.js

ssm.min.js

250 ms

sticky_header.js

sticky_header.js

263 ms

open-sans-v17-latin-regular.woff

open-sans-v17-latin-regular.woff

309 ms

OpenSans-Light.woff

OpenSans-Light.woff

319 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

334 ms

open-sans-v17-latin-800.woff

open-sans-v17-latin-800.woff

331 ms

logo.svg

logo.svg

264 ms

liveChat-open.png

liveChat-open.png

310 ms

icon-location.png

icon-location.png

325 ms

icon-track.png

icon-track.png

313 ms

icon-login.png

icon-login.png

333 ms

logo-small.png

logo-small.png

298 ms

icon-linkedin.png

icon-linkedin.png

301 ms

icon-twitter.png

icon-twitter.png

335 ms

icon-facebook.png

icon-facebook.png

308 ms

icon-instagram.png

icon-instagram.png

312 ms

icon-appstore.png

icon-appstore.png

194 ms

icon-googleplay.png

icon-googleplay.png

201 ms

banner_0.png

banner_0.png

282 ms

tracker-icon.png

tracker-icon.png

254 ms

shipGuest.png

shipGuest.png

274 ms

estimate.png

estimate.png

273 ms

payBills.png

payBills.png

235 ms

BHM-story3.jpeg

BHM-story3.jpeg

286 ms

Release%20header.jpg

Release%20header.jpg

317 ms

h-uoft-campus.jpg

h-uoft-campus.jpg

347 ms

rr-reverse-logistics-returns.jpg

rr-reverse-logistics-returns.jpg

317 ms

rr-lean-logistics.png

rr-lean-logistics.png

351 ms

rr-freight-logistics-consolidation.png

rr-freight-logistics-consolidation.png

406 ms

icon-online-shipping.png

icon-online-shipping.png

328 ms

fa-solid-900.woff

fa-solid-900.woff

394 ms

fa-regular-400.woff

fa-regular-400.woff

403 ms

icon-piggy-bank.png

icon-piggy-bank.png

430 ms

icon-online-shipping.png

icon-online-shipping.png

378 ms

icon-credit-card.png

icon-credit-card.png

426 ms

x3_0.png

x3_0.png

417 ms

purolator_logo.png

purolator_logo.png

419 ms

main.js

main.js

29 ms

Accessibility Review

billingcentre.purolator.com accessibility score

87

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-hidden="true"] elements contain focusable descendents

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

billingcentre.purolator.com best practices score

83

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

Page has valid source maps

SEO Factors

billingcentre.purolator.com SEO score

84

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 Billingcentre.purolator.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 Billingcentre.purolator.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

billingcentre.purolator.com

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