Tools & Wizards About Us
torontoist.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

torontoist.com

Daily Hive | Torontoist

Page Load Speed

961 ms in total

First Response

56 ms

Resources Loaded

826 ms

Page Rendered

79 ms

torontoist.com screenshot

About Website

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

The Torontoist was sold to Daily Hive

Visit torontoist.com

Key Findings

We analyzed Torontoist.com page load time and found that the first response time was 56 ms and then it took 905 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

torontoist.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value1,800 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

torontoist.com

56 ms

torontoist

401 ms

a39f7ccd2dd21d15.css

19 ms

560c4da6c277a49c.css

59 ms

polyfills-c67a75d1b6f99dc8.js

32 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Torontoist.com, 46% (12 requests) were made to Dailyhive.com and 31% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (401 ms) relates to the external source Dailyhive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.5 kB (69%)

Content Size

12.3 kB

After Optimization

3.8 kB

  • HTML
  • CSS

In fact, the total size of Torontoist.com main page is 12.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 11.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 8.3 kB

  • Original 11.6 kB
  • After minification 11.6 kB
  • After compression 3.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. 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 8.3 kB or 72% of the original size.

CSS Optimization

-17%

Potential reduce by 129 B

  • Original 739 B
  • After minification 739 B
  • After compression 610 B

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. Torontoist.com needs all CSS files to be minified and compressed as it can save up to 129 B or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (69%)

Requests Now

16

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

torontoist.com

torontoist.com

56 ms

torontoist

torontoist

401 ms

a39f7ccd2dd21d15.css

a39f7ccd2dd21d15.css

19 ms

560c4da6c277a49c.css

560c4da6c277a49c.css

59 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

32 ms

webpack-0d02493dddb8888b.js

webpack-0d02493dddb8888b.js

60 ms

framework-314c182fa7e2bf37.js

framework-314c182fa7e2bf37.js

64 ms

main-df3d0c701e3abd94.js

main-df3d0c701e3abd94.js

72 ms

_app-2d4e5fad3d1d0bdc.js

_app-2d4e5fad3d1d0bdc.js

71 ms

3719-0a37f95b25fe8aec.js

3719-0a37f95b25fe8aec.js

79 ms

torontoist-52b4a16a6ad8ba86.js

torontoist-52b4a16a6ad8ba86.js

81 ms

_buildManifest.js

_buildManifest.js

82 ms

_ssgManifest.js

_ssgManifest.js

81 ms

dailyhive-color-white.svg

dailyhive-color-white.svg

72 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

98 ms

style.css

style.css

74 ms

18EOEwAQAQ4_momently.js

18EOEwAQAQ4_momently.js

284 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4KLg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4KLg.woff

19 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4KLjztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4KLjztg.woff

25 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4KLjztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4KLjztg.woff

27 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4KLjztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4KLjztg.woff

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4KLjztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4KLjztg.woff

31 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

31 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

35 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

31 ms

momently.js

momently.js

75 ms

Accessibility Review

torontoist.com accessibility score

97

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.

Best Practices

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

torontoist.com SEO score

100

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

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

torontoist.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: