878 ms in total
3 ms
797 ms
78 ms
Visit staplesswag.ca now to see the best up-to-date Staples Swag content and also check out these interesting facts you probably never knew about staplesswag.ca
Elevate your brand with our promotional products. Personalize your items and leave a lasting impression on your clients. Make your brand stand out today.
Visit staplesswag.caWe analyzed Staplesswag.ca page load time and found that the first response time was 3 ms and then it took 875 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
staplesswag.ca performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value16.8 s
0/100
25%
Value11.6 s
4/100
10%
Value9,680 ms
0/100
30%
Value0.473
18/100
15%
Value22.1 s
1/100
10%
3 ms
119 ms
31 ms
39 ms
56 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Staplesswag.ca, 63% (24 requests) were made to Shop.staplescopyandprint.ca and 16% (6 requests) were made to Staplescopyandprint.ca. The less responsive or slowest element that took the longest time to load (371 ms) relates to the external source Cdn.segment.com.
Page size can be reduced by 395.3 kB (33%)
1.2 MB
818.4 kB
In fact, the total size of Staplesswag.ca main page is 1.2 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. 65% of websites need less resources to load. Javascripts take 892.7 kB which makes up the majority of the site volume.
Potential reduce by 185.4 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 185.4 kB or 76% of the original size.
Potential reduce by 192.1 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 192.1 kB or 22% of the original size.
Potential reduce by 17.8 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. Staplesswag.ca needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 24% of the original size.
Number of requests can be reduced by 31 (86%)
36
5
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Staples Swag. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
staplesswag.ca
3 ms
staples-custom-merchandise
119 ms
datadog-rum-v4.js
31 ms
theme.css
39 ms
main.css
56 ms
preloads.js
72 ms
load_feature-87876fa245af19cbd14aa886ed59c6aa8a27c45d24dcd7a81cf2d2323506233e.js
53 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
51 ms
vendor-scripts-v0.js
66 ms
bundle.runtime.js
68 ms
bundle.main.js
71 ms
algolia_config.js
75 ms
algolia_dependency_font-awesome-4-4-0.min.css
65 ms
algolia_externals.js
72 ms
algolia_init.js
80 ms
algolia_analytics.js
163 ms
algolia_translations.js
164 ms
algolia_helpers.js
164 ms
algolia_autocomplete.js
165 ms
algolia_facets.js
165 ms
algolia_sort_orders.js
166 ms
algolia_instant_search.js
167 ms
identify.js
173 ms
trekkie.storefront.d88aa5f007759294e4f3b66e32cebf97843d3efb.min.js
97 ms
shop_events_listener-a7c63dba65ccddc484f77541dc8ca437e60e1e9e297fe1c3faebf6523a0ede9b.js
97 ms
shopify-boomerang-1.0.0.min.js
93 ms
analytics.min.js
371 ms
header
162 ms
footer
214 ms
1ce2d577-6659-46e1-817f-9e081542547a.js
113 ms
main.36cd79bf.css
45 ms
rocket-loader.min.js
23 ms
analytics.min.js
339 ms
main.565dc2a1.js
45 ms
main.js
21 ms
settings
3 ms
staples-canada-dev3.js
32 ms
index.min.js
59 ms
staplesswag.ca accessibility score
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
Links do not have a discernible name
staplesswag.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
staplesswag.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Staplesswag.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 Staplesswag.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.
staplesswag.ca
Open Graph data is detected on the main page of Staples Swag. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: