4.8 sec in total
45 ms
1.8 sec
2.9 sec
Click here to check amazing Thespec content for Canada. Otherwise, check out these important facts you probably never knew about thespec.ca
Visit thespec.caWe analyzed Thespec.ca page load time and found that the first response time was 45 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
thespec.ca performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value8.9 s
1/100
25%
Value11.7 s
4/100
10%
Value4,350 ms
1/100
30%
Value0.016
100/100
15%
Value31.5 s
0/100
10%
45 ms
197 ms
86 ms
98 ms
112 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Thespec.ca, 53% (55 requests) were made to Bloximages.chicago2.vip.townnews.com and 7% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (652 ms) relates to the external source Api.segment.io.
Page size can be reduced by 673.8 kB (39%)
1.7 MB
1.1 MB
In fact, the total size of Thespec.ca main page is 1.7 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. 80% 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. Javascripts take 603.2 kB which makes up the majority of the site volume.
Potential reduce by 530.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 106.3 kB, which is 18% 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 530.2 kB or 89% of the original size.
Potential reduce by 0 B
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. Thespec images are well optimized though.
Potential reduce by 132.2 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 132.2 kB or 22% of the original size.
Potential reduce by 11.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. Thespec.ca needs all CSS files to be minified and compressed as it can save up to 11.5 kB or 19% of the original size.
Number of requests can be reduced by 55 (56%)
98
43
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thespec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
thespec.ca
45 ms
www.thespec.com
197 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
86 ms
layout.5bce7eb56c23d79d6ab89ab093c281ea.css
98 ms
oovvuu.css
112 ms
flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css
111 ms
access.d7adebba498598b0ec2c.js
82 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
118 ms
user.js
142 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
117 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
141 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
154 ms
application.3c64d611e594b45dd35b935162e79d85.js
153 ms
polyfill.min.js
310 ms
footer.nav.js
153 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
163 ms
gpt.js
237 ms
18488.js
167 ms
liftigniter.min.js
157 ms
promo_popup.min.js
155 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
160 ms
tracking.js
136 ms
save.asset.js
160 ms
index.js
109 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
162 ms
amp-iframe-0.1.js
108 ms
launch-9387fe3a1e9f.min.js
151 ms
css2
146 ms
tracker.js
158 ms
get.js
118 ms
newsletter-helper.min.js
127 ms
tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js
126 ms
sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js
134 ms
tnt.regions.b44801b45845a81b995eeaad12f4f276.js
133 ms
gtm.js
69 ms
analytics.js
19 ms
gtm.js
25 ms
gtm.js
108 ms
publisher:getClientId
157 ms
apstag.js
162 ms
channels.cgi
310 ms
gtm.js
298 ms
c0094646-1108-11ee-8af0-b3954ce40e5e.png
148 ms
43343e3e-8d12-11ed-8c1b-53f33b76259d.png
148 ms
432e2d00-8d12-11ed-8c1a-b30f6a5cad27.png
146 ms
6646987ca4c18.image.jpg
150 ms
66465498977f3.image.jpg
147 ms
6647afed11ce3.image.jpg
149 ms
66463d0e3ae1d.image.jpg
152 ms
6644d2daf20e9.image.jpg
152 ms
664674e3673d0.image.jpg
152 ms
6644dc2585e3a.image.jpg
152 ms
5f0e35de-eab7-11ee-8e0c-43517d596b49.jpg
153 ms
ee1461aa-a1bf-11ed-a274-ab429d1e83d9.886161bdaa9ae605f2d693996beacfa1.png
153 ms
299ebe5c-a0e2-11ed-a5f0-dbe7c3d9724e.6b32a31fe9ab2776214aceb62d7e098a.png
295 ms
664635ee75090.image.jpg
294 ms
664534859f4d3.image.jpg
292 ms
6634fb428f5ae.image.jpg
293 ms
6647e1dcd58d4.image.jpg
294 ms
6647e1dcd58d4.image.jpg
292 ms
662d6cbb7802e.image.jpg
298 ms
66475079b67e9.image.jpg
300 ms
664758522bfd6.image.jpg
299 ms
664649f79c237.image.jpg
297 ms
663a02273f1d4.image.jpg
464 ms
6628736ae388a.image.jpg
465 ms
661ea5b10a8cc.image.jpg
465 ms
66212ea3956cc.image.jpg
465 ms
663d3c3dbd9e1.image.jpg
465 ms
661ecabb69476.image.jpg
465 ms
6647e3355b4d1.image.jpg
540 ms
6647e2db74257.image.jpg
539 ms
6647e2e62144b.image.jpg
540 ms
4481840e-8d12-11ed-8c26-ab83b7277b30.png
539 ms
todays-paper.png
540 ms
app-store.svg
538 ms
google-play.svg
551 ms
tracker.gif
144 ms
pubads_impl.js
107 ms
collect
212 ms
collect
466 ms
analytics.min.js
184 ms
destination
175 ms
apstag.js
324 ms
58580620
325 ms
web-vitals.iife.js
79 ms
settings
29 ms
870.bundle.6e2976b75e60ab2b2bf8.js
10 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
10 ms
web-vitals.iife.js
51 ms
m
652 ms
AGSKWxU8BxTqUCuQjLDpESbkxjsxtT9bkoKpZubtUVIH4lKJOVAZCIVuuS8mzM7mLX0pk4Wh-cl5OsywxspcwRy_8_JqA1_MV8iuQrufcfL-apKCz4PXnrXhiUJtz1wNFB785BQL5rypaA==
54 ms
esp.js
224 ms
esp.js
223 ms
uid2SecureSignal.js
222 ms
10912.jsx
274 ms
AGSKWxWtHUzsbHbUiNFee68IifFq69n8tmKj7iLT5pfIVHdeIBDdJkyWwOsFPosYHGsSjNeNuaDnoE53xOT2i-w03jyEek57VmO-C8uPq3uKYPAEiOrBf3q0o8UAIe0SA-2RPcHaYSOYOw==
109 ms
js
106 ms
js
99 ms
WidgetTemplate2.min.css
16 ms
jquery.fireSlider.min.js
15 ms
rad.js
16 ms
css
207 ms
thespec.ca accessibility score
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
[aria-*] attributes do not match their roles
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
thespec.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
thespec.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thespec.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 Thespec.ca main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
thespec.ca
Open Graph description is not detected on the main page of Thespec. 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: