Tools & Wizards About Us
torontoplace.com screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

torontoplace.com

Toronto Ontario Canada city guide to weather, map, hotels, restaurants and business

Page Load Speed

579 ms in total

First Response

122 ms

Resources Loaded

331 ms

Page Rendered

126 ms

torontoplace.com screenshot

About Website

Click here to check amazing Toronto Place content. Otherwise, check out these important facts you probably never knew about torontoplace.com

Your guide to Toronto. Includes weather, maps, hotels, restaurants, movies, businesses, news and anything else to do with Toronto.

Visit torontoplace.com

Key Findings

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

Performance Metrics

torontoplace.com performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

torontoplace.com

122 ms

tpstyles.css

39 ms

style.css

31 ms

container.css

36 ms

banner_spcr.jpg

26 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 96% of them (65 requests) were addressed to the original Torontoplace.com, 1% (1 request) were made to Torontogasprices.com and 1% (1 request) were made to Statcounter.com. The less responsive or slowest element that took the longest time to load (147 ms) belongs to the original domain Torontoplace.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.5 kB (20%)

Content Size

266.4 kB

After Optimization

212.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Torontoplace.com main page is 266.4 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. Images take 206.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 45.4 kB

  • Original 51.9 kB
  • After minification 40.7 kB
  • After compression 6.5 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 11.2 kB, which is 22% 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 45.4 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 2.5 kB

  • Original 206.6 kB
  • After minification 204.1 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 Place images are well optimized though.

CSS Optimization

-82%

Potential reduce by 6.5 kB

  • Original 7.9 kB
  • After minification 6.5 kB
  • After compression 1.4 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. Torontoplace.com needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (49%)

Requests Now

67

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

torontoplace.com

torontoplace.com

122 ms

tpstyles.css

tpstyles.css

39 ms

style.css

style.css

31 ms

container.css

container.css

36 ms

banner_spcr.jpg

banner_spcr.jpg

26 ms

Torontogasbuddy.gif

Torontogasbuddy.gif

66 ms

counter.js

counter.js

24 ms

menu_left.jpg

menu_left.jpg

26 ms

menu_right.jpg

menu_right.jpg

23 ms

housing.gif

housing.gif

50 ms

specialevents.jpg

specialevents.jpg

47 ms

ttc.jpg

ttc.jpg

32 ms

canadapost.jpg

canadapost.jpg

28 ms

canada411.jpg

canada411.jpg

50 ms

clubumbrella.jpg

clubumbrella.jpg

47 ms

ey.jpg

ey.jpg

50 ms

adplacement.jpg

adplacement.jpg

52 ms

zandi4.jpg

zandi4.jpg

51 ms

adricho.jpg

adricho.jpg

53 ms

ca_flag.gif

ca_flag.gif

51 ms

aflgspacer.gif

aflgspacer.gif

61 ms

fr.gif

fr.gif

64 ms

es_sp.gif

es_sp.gif

67 ms

it.gif

it.gif

68 ms

el.gif

el.gif

67 ms

pt_pt.gif

pt_pt.gif

68 ms

mex_flag.gif

mex_flag.gif

71 ms

de.gif

de.gif

68 ms

zh.gif

zh.gif

75 ms

ja.gif

ja.gif

75 ms

ko.gif

ko.gif

76 ms

rus.gif

rus.gif

76 ms

cze_flag.gif

cze_flag.gif

81 ms

saudi_flag.gif

saudi_flag.gif

76 ms

turkey-flag.gif

turkey-flag.gif

83 ms

pl_flag.gif

pl_flag.gif

81 ms

rom_flag.gif

rom_flag.gif

82 ms

hu_flag.gif

hu_flag.gif

82 ms

serb_flag.gif

serb_flag.gif

83 ms

flowers141x175.gif

flowers141x175.gif

24 ms

menu_left.jpg

menu_left.jpg

17 ms

classifedes.jpg

classifedes.jpg

24 ms

menu_right.jpg

menu_right.jpg

18 ms

personals.jpg

personals.jpg

22 ms

fun.jpg

fun.jpg

22 ms

bullet.jpg

bullet.jpg

44 ms

other.jpg

other.jpg

42 ms

ebooks.jpg

ebooks.jpg

44 ms

slovenia_flag.gif

slovenia_flag.gif

73 ms

swe_flag.GIF

swe_flag.GIF

69 ms

fi_flag.gif

fi_flag.gif

69 ms

flag_norway.gif

flag_norway.gif

66 ms

den_flag.gif

den_flag.gif

66 ms

nl.gif

nl.gif

63 ms

t.php

t.php

76 ms

flag_phillipines.gif

flag_phillipines.gif

59 ms

banner_tile.jpg

banner_tile.jpg

12 ms

menu_bg.jpg

menu_bg.jpg

11 ms

bg1.jpg

bg1.jpg

9 ms

bg.jpg

bg.jpg

147 ms

bg2.jpg

bg2.jpg

8 ms

left-bg.jpg

left-bg.jpg

11 ms

btmBar.jpg

btmBar.jpg

28 ms

sfweblogo.jpg

sfweblogo.jpg

57 ms

banner_new.jpg

banner_new.jpg

57 ms

menu-bg.jpg

menu-bg.jpg

51 ms

menu_bg.jpg

menu_bg.jpg

50 ms

left-bg.jpg

left-bg.jpg

48 ms

Accessibility Review

torontoplace.com accessibility score

52

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

torontoplace.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

torontoplace.com SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torontoplace.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Torontoplace.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

torontoplace.com

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