Tools & Wizards About Us
cambridgesurplus.ca screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    32% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 88

    SEO

    Google-friendlier than
    71% of websites

cambridgesurplus.ca

Cambridge Surplus

Page Load Speed

15.7 sec in total

First Response

955 ms

Resources Loaded

13.1 sec

Page Rendered

1.6 sec

cambridgesurplus.ca screenshot

About Website

Welcome to cambridgesurplus.ca homepage info - get ready to check Cambridge Surplus best content right away, or after learning these important things about cambridgesurplus.ca

Visit cambridgesurplus.ca

Key Findings

We analyzed Cambridgesurplus.ca page load time and found that the first response time was 955 ms and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

cambridgesurplus.ca performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value24.0 s

0/100

10%

TBT (Total Blocking Time)

Value22,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.145

77/100

15%

TTI (Time to Interactive)

Value33.6 s

0/100

10%

Network Requests Diagram

cambridgesurplus.ca

955 ms

css

158 ms

style.css

89 ms

font-awesome.min.css

133 ms

media-queries.css

181 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 63% of them (66 requests) were addressed to the original Cambridgesurplus.ca, 11% (12 requests) were made to S3.wasabisys.com and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Cambridgesurplus.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (50%)

Content Size

2.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cambridgesurplus.ca main page is 2.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.9 kB

  • Original 66.0 kB
  • After minification 63.6 kB
  • After compression 15.0 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 50.9 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 53.0 kB

  • Original 1.2 MB
  • After minification 1.1 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. Cambridge Surplus images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 145.4 kB

  • Original 229.8 kB
  • After minification 228.5 kB
  • After compression 84.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 145.4 kB or 63% of the original size.

CSS Optimization

-86%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 181.7 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. Cambridgesurplus.ca needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (79%)

Requests Now

92

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cambridgesurplus.ca

cambridgesurplus.ca

955 ms

css

css

158 ms

style.css

style.css

89 ms

font-awesome.min.css

font-awesome.min.css

133 ms

media-queries.css

media-queries.css

181 ms

style.min.css

style.min.css

414 ms

style.min.css

style.min.css

320 ms

css

css

311 ms

style.min.css

style.min.css

386 ms

style.min.css

style.min.css

318 ms

style.min.css

style.min.css

382 ms

mediacloud-mux.blocks.style.css

mediacloud-mux.blocks.style.css

385 ms

vendors-style.css

vendors-style.css

443 ms

style.css

style.css

455 ms

font-awesome.min.css

font-awesome.min.css

433 ms

nivo-lightbox.css

nivo-lightbox.css

420 ms

default.css

default.css

440 ms

woocommerce-layout.css

woocommerce-layout.css

419 ms

woocommerce.css

woocommerce.css

514 ms

mcloud-elementor.css

mcloud-elementor.css

501 ms

jquery.sidr.dark.css

jquery.sidr.dark.css

487 ms

elementor-icons.min.css

elementor-icons.min.css

485 ms

animations.min.css

animations.min.css

511 ms

frontend-legacy.min.css

frontend-legacy.min.css

519 ms

frontend.min.css

frontend.min.css

519 ms

post-49017.css

post-49017.css

537 ms

frontend.min.css

frontend.min.css

568 ms

all.min.css

all.min.css

528 ms

v4-shims.min.css

v4-shims.min.css

560 ms

global.css

global.css

563 ms

post-2.css

post-2.css

564 ms

css

css

283 ms

jquery.js

jquery.js

658 ms

v4-shims.min.js

v4-shims.min.js

532 ms

theme.script.js

theme.script.js

625 ms

formreset.min.css

formreset.min.css

623 ms

formsmain.min.css

formsmain.min.css

687 ms

readyclass.min.css

readyclass.min.css

690 ms

browsers.min.css

browsers.min.css

690 ms

api.js

api.js

394 ms

nivo-lightbox.min.js

nivo-lightbox.min.js

689 ms

script.js

script.js

625 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

642 ms

add-to-cart.min.js

add-to-cart.min.js

489 ms

js.cookie.min.js

js.cookie.min.js

400 ms

woocommerce.min.js

woocommerce.min.js

368 ms

cart-fragments.min.js

cart-fragments.min.js

391 ms

jquery.sidr.min.js

jquery.sidr.min.js

385 ms

jquery.sidr.min.init.js

jquery.sidr.min.init.js

390 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

391 ms

jquery.touchwipe.min.init.js

jquery.touchwipe.min.init.js

638 ms

wp-embed.min.js

wp-embed.min.js

370 ms

comment-reply.min.js

comment-reply.min.js

370 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

368 ms

frontend-modules.min.js

frontend-modules.min.js

359 ms

jquery.sticky.min.js

jquery.sticky.min.js

324 ms

frontend.min.js

frontend.min.js

324 ms

position.min.js

position.min.js

309 ms

dialog.min.js

dialog.min.js

301 ms

waypoints.min.js

waypoints.min.js

296 ms

swiper.min.js

swiper.min.js

296 ms

share-link.min.js

share-link.min.js

269 ms

frontend.min.js

frontend.min.js

264 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

261 ms

siq-container-2.js

siq-container-2.js

328 ms

ppe1.jpg

ppe1.jpg

1219 ms

header-text.png

header-text.png

92 ms

ppe4.jpg

ppe4.jpg

1301 ms

ppe5.jpg

ppe5.jpg

1216 ms

ppe7.jpg

ppe7.jpg

1222 ms

ppe2.jpg

ppe2.jpg

1314 ms

ppe8.jpg

ppe8.jpg

1306 ms

ppe3.jpg

ppe3.jpg

1304 ms

ppe6.jpg

ppe6.jpg

1302 ms

09212020-CRAYOLA-GEL-PENS-20-418x500.jpg

09212020-CRAYOLA-GEL-PENS-20-418x500.jpg

1299 ms

eDCgWdhg-09212020-CRAYOLA-COLOR-PENCILS-24-437x500.jpg

eDCgWdhg-09212020-CRAYOLA-COLOR-PENCILS-24-437x500.jpg

1552 ms

09212020-CRAYOLA-BLENDING-MARKERS-407x500.jpg

09212020-CRAYOLA-BLENDING-MARKERS-407x500.jpg

1551 ms

09212020-CRAYOLA-BLEND-COLOR-PENCILS-50-500x402.jpg

09212020-CRAYOLA-BLEND-COLOR-PENCILS-50-500x402.jpg

1542 ms

sdk.js

sdk.js

1134 ms

analytics.js

analytics.js

1172 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rl.woff

1114 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rl.woff

1203 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rl.woff

1366 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISmb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISmb2Rl.woff

1355 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rl.woff

1366 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rl.woff

1360 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rl.woff

1365 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOmb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOmb2Rl.woff

1436 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rl.woff

1436 ms

fa-solid-900.woff

fa-solid-900.woff

816 ms

fa-regular-400.woff

fa-regular-400.woff

785 ms

settings

settings

983 ms

recaptcha__en.js

recaptcha__en.js

984 ms

cambridgesurplus.ca

cambridgesurplus.ca

1940 ms

frontend-msie.min.css

frontend-msie.min.css

376 ms

sdk.js

sdk.js

178 ms

collect

collect

358 ms

collect

collect

250 ms

sa.js

sa.js

195 ms

autocomplete.js

autocomplete.js

195 ms

live

live

176 ms

autocomplete.css

autocomplete.css

12 ms

custom.css

custom.css

142 ms

stylesheet.css

stylesheet.css

26 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

13 ms

Accessibility Review

cambridgesurplus.ca accessibility score

96

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

cambridgesurplus.ca SEO score

88

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

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 Cambridgesurplus.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 Cambridgesurplus.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

cambridgesurplus.ca

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