Tools & Wizards About Us
torontogrand.ca screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

torontogrand.ca

Toronto Grand Banquet Hall & Convention Centre – Toronto Banquet Hall & Event Venue

Page Load Speed

1.1 sec in total

First Response

12 ms

Resources Loaded

605 ms

Page Rendered

469 ms

torontogrand.ca screenshot

About Website

Welcome to torontogrand.ca homepage info - get ready to check Toronto Grand best content right away, or after learning these important things about torontogrand.ca

Visit torontogrand.ca

Key Findings

We analyzed Torontogrand.ca page load time and found that the first response time was 12 ms and then it took 1.1 sec 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.

Performance Metrics

torontogrand.ca performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

torontogrand.ca

12 ms

torontogrand.ca

207 ms

wp-emoji-release.min.js

12 ms

dripicons.min.css

19 ms

elegant-icons.min.css

23 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 70% of them (48 requests) were addressed to the original Torontogrand.ca, 22% (15 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (207 ms) belongs to the original domain Torontogrand.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.8 kB (5%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Torontogrand.ca main page is 1.4 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. Images take 810.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 53.4 kB

  • Original 64.9 kB
  • After minification 64.0 kB
  • After compression 11.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. 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 53.4 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 15.2 kB

  • Original 810.5 kB
  • After minification 795.3 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 Grand images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 354.7 kB
  • After minification 354.7 kB
  • After compression 351.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

-1%

Potential reduce by 1.4 kB

  • Original 150.6 kB
  • After minification 150.2 kB
  • After compression 149.2 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. Torontogrand.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 42 (82%)

Requests Now

51

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

torontogrand.ca

torontogrand.ca

12 ms

torontogrand.ca

torontogrand.ca

207 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

12 ms

dripicons.min.css

dripicons.min.css

19 ms

elegant-icons.min.css

elegant-icons.min.css

23 ms

all.min.css

all.min.css

19 ms

ionicons.min.css

ionicons.min.css

23 ms

linea-icons.min.css

linea-icons.min.css

25 ms

linear-icons.min.css

linear-icons.min.css

25 ms

icon

icon

76 ms

simple-line-icons.min.css

simple-line-icons.min.css

30 ms

style.min.css

style.min.css

30 ms

classic-themes.min.css

classic-themes.min.css

33 ms

styles.css

styles.css

33 ms

select2.min.css

select2.min.css

29 ms

core-dashboard.min.css

core-dashboard.min.css

29 ms

main.min.css

main.min.css

41 ms

banquet-core.min.css

banquet-core.min.css

35 ms

style.css

style.css

34 ms

swiper.min.css

swiper.min.css

40 ms

magnific-popup.css

magnific-popup.css

33 ms

css

css

78 ms

js_composer.min.css

js_composer.min.css

56 ms

jquery.min.js

jquery.min.js

69 ms

jquery-migrate.min.js

jquery-migrate.min.js

69 ms

index.js

index.js

70 ms

index.js

index.js

72 ms

hoverIntent.min.js

hoverIntent.min.js

70 ms

core.min.js

core.min.js

71 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

68 ms

modernizr.js

modernizr.js

70 ms

main.min.js

main.min.js

72 ms

banquet-core.min.js

banquet-core.min.js

71 ms

jquery.waitforimages.js

jquery.waitforimages.js

70 ms

jquery.appear.js

jquery.appear.js

72 ms

swiper.min.js

swiper.min.js

72 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

73 ms

api.js

api.js

76 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

73 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

73 ms

wp-polyfill.min.js

wp-polyfill.min.js

73 ms

index.js

index.js

66 ms

js_composer_front.min.js

js_composer_front.min.js

59 ms

jquery.parallax-scroll.js

jquery.parallax-scroll.js

59 ms

skrollr.min.js

skrollr.min.js

55 ms

tgc-logo-large.png

tgc-logo-large.png

135 ms

h1-slider-img-2.jpg

h1-slider-img-2.jpg

134 ms

recaptcha__en.js

recaptcha__en.js

93 ms

website-logo-1.png

website-logo-1.png

72 ms

p7-img-1.jpg

p7-img-1.jpg

79 ms

blog-1-img-2.jpg

blog-1-img-2.jpg

79 ms

blog-img-5.jpg

blog-img-5.jpg

72 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

134 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

141 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

160 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

161 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

177 ms

co3ZmX5slCNuHLi8bLeY9MK7whWMhyjYrEtGmS8.ttf

co3ZmX5slCNuHLi8bLeY9MK7whWMhyjYrEtGmS8.ttf

177 ms

co3WmX5slCNuHLi8bLeY9MK7whWMhyjYrEO7uj-EzhY.ttf

co3WmX5slCNuHLi8bLeY9MK7whWMhyjYrEO7uj-EzhY.ttf

176 ms

co3WmX5slCNuHLi8bLeY9MK7whWMhyjYrEPjuz-EzhY.ttf

co3WmX5slCNuHLi8bLeY9MK7whWMhyjYrEPjuz-EzhY.ttf

177 ms

co3WmX5slCNuHLi8bLeY9MK7whWMhyjYrEOXvT-EzhY.ttf

co3WmX5slCNuHLi8bLeY9MK7whWMhyjYrEOXvT-EzhY.ttf

176 ms

co3WmX5slCNuHLi8bLeY9MK7whWMhyjYrEPzvD-EzhY.ttf

co3WmX5slCNuHLi8bLeY9MK7whWMhyjYrEPzvD-EzhY.ttf

175 ms

co3bmX5slCNuHLi8bLeY9MK7whWMhyjYp3tP.ttf

co3bmX5slCNuHLi8bLeY9MK7whWMhyjYp3tP.ttf

196 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfsA-N.ttf

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfsA-N.ttf

177 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfsA-N.ttf

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfsA-N.ttf

196 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fsA-N.ttf

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fsA-N.ttf

196 ms

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fsA-N.ttf

co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fsA-N.ttf

196 ms

h1-parallax-img-1.jpg

h1-parallax-img-1.jpg

68 ms

h1-slider-img-2.jpg

h1-slider-img-2.jpg

71 ms

Accessibility Review

torontogrand.ca accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

torontogrand.ca 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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

torontogrand.ca SEO score

86

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

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

Social Sharing Optimization

torontogrand.ca

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