Tools & Wizards About Us
torontostar.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

torontostar.com

Breaking News - Headlines & Top Stories | The Star

Page Load Speed

3.6 sec in total

First Response

68 ms

Resources Loaded

1.3 sec

Page Rendered

2.2 sec

torontostar.com screenshot

About Website

Welcome to torontostar.com homepage info - get ready to check Toronto Star best content right away, or after learning these important things about torontostar.com

thestar.com is Canada’s largest online news site. Live news, investigations, politics, sports and the heartbeat of Toronto, Canada's largest city.

Visit torontostar.com

Key Findings

We analyzed Torontostar.com page load time and found that the first response time was 68 ms and then it took 3.5 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

torontostar.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value7,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.233

53/100

15%

TTI (Time to Interactive)

Value40.0 s

0/100

10%

Network Requests Diagram

torontostar.com

68 ms

www.thestar.com

186 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

159 ms

layout.d9bf9fa5b377514df7224a864456e96d.css

167 ms

oovvuu.css

164 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Torontostar.com, 52% (32 requests) were made to Bloximages.chicago2.vip.townnews.com and 10% (6 requests) were made to Thestar.com. The less responsive or slowest element that took the longest time to load (548 ms) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 544.7 kB (31%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Torontostar.com main page is 1.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. 75% 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 935.7 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 508.7 kB

  • Original 578.0 kB
  • After minification 483.7 kB
  • After compression 69.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. This page needs HTML code to be minified as it can gain 94.3 kB, which is 16% 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 508.7 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 188.2 kB
  • After minification 188.2 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. Toronto Star images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 24.8 kB

  • Original 935.7 kB
  • After minification 935.6 kB
  • After compression 910.9 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

-19%

Potential reduce by 11.2 kB

  • Original 57.9 kB
  • After minification 57.9 kB
  • After compression 46.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. Torontostar.com needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

torontostar.com

torontostar.com

68 ms

www.thestar.com

www.thestar.com

186 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

159 ms

layout.d9bf9fa5b377514df7224a864456e96d.css

layout.d9bf9fa5b377514df7224a864456e96d.css

167 ms

oovvuu.css

oovvuu.css

164 ms

flex-utility-text-promo.945a2efac4892ce469180c513f411107.css

flex-utility-text-promo.945a2efac4892ce469180c513f411107.css

164 ms

flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css

flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css

165 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

117 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

163 ms

user.js

user.js

142 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

187 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

191 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

193 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

194 ms

polyfill.min.js

polyfill.min.js

548 ms

tag

tag

138 ms

thestar-sdk.js

thestar-sdk.js

142 ms

edition-selector.js

edition-selector.js

192 ms

footer.nav.js

footer.nav.js

193 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

194 ms

gpt.js

gpt.js

197 ms

18488.js

18488.js

157 ms

liftigniter.min.js

liftigniter.min.js

193 ms

api.js

api.js

142 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

192 ms

tracking.js

tracking.js

139 ms

save.asset.js

save.asset.js

192 ms

index.js

index.js

134 ms

fontawesome.568f3d1ab17b33ce05854081baadadac.js

fontawesome.568f3d1ab17b33ce05854081baadadac.js

198 ms

amp-iframe-0.1.js

amp-iframe-0.1.js

128 ms

client

client

187 ms

swg.js

swg.js

132 ms

launch-9387fe3a1e9f.min.js

launch-9387fe3a1e9f.min.js

129 ms

css2

css2

176 ms

tracker.js

tracker.js

169 ms

newsletter-helper.min.js

newsletter-helper.min.js

180 ms

tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js

tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js

180 ms

sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js

sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js

178 ms

tnt.regions.b44801b45845a81b995eeaad12f4f276.js

tnt.regions.b44801b45845a81b995eeaad12f4f276.js

178 ms

promo_popup.min.js

promo_popup.min.js

178 ms

tag

tag

64 ms

gtm.js

gtm.js

62 ms

apstag.js

apstag.js

69 ms

channels.cgi

channels.cgi

331 ms

gtm.js

gtm.js

64 ms

31c48758-8d44-11ed-8c30-0bcb8697ec11.png

31c48758-8d44-11ed-8c30-0bcb8697ec11.png

59 ms

6665f430ea010.image.jpg

6665f430ea010.image.jpg

60 ms

66634d02db8c2.image.jpg

66634d02db8c2.image.jpg

61 ms

7cfc38ca-9d1a-11ed-8f0b-5cb9017b77dc.a0b13c4b7a02e09c478fe74111026137.png

7cfc38ca-9d1a-11ed-8f0b-5cb9017b77dc.a0b13c4b7a02e09c478fe74111026137.png

58 ms

445a0c88-a240-11ed-aa66-33cbdfca79af.68b00ff74032ee7b477665d549da5b2f.png

445a0c88-a240-11ed-aa66-33cbdfca79af.68b00ff74032ee7b477665d549da5b2f.png

57 ms

8cd8cf22-a28a-11ed-8d9b-a79d6194e329.27c424c21240b3ba208f883c061681f9.png

8cd8cf22-a28a-11ed-8d9b-a79d6194e329.27c424c21240b3ba208f883c061681f9.png

57 ms

2faeee7c-8d44-11ed-8c18-eb5483a10695.png

2faeee7c-8d44-11ed-8c18-eb5483a10695.png

203 ms

todays-paper.png

todays-paper.png

106 ms

app-store.svg

app-store.svg

199 ms

google-play.svg

google-play.svg

200 ms

pubads_impl.js

pubads_impl.js

73 ms

recaptcha__en.js

recaptcha__en.js

168 ms

tracker.gif

tracker.gif

156 ms

web-vitals.iife.js

web-vitals.iife.js

164 ms

58580620

58580620

224 ms

web-vitals.iife.js

web-vitals.iife.js

23 ms

Accessibility Review

torontostar.com accessibility score

83

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-*] attributes do not match their roles

High

[role]s are not contained by their required parent element

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.

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

<frame> or <iframe> elements do not have a title

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

torontostar.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torontostar.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 Torontostar.com 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.

Social Sharing Optimization

torontostar.com

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