8.5 sec in total
1.4 sec
6.5 sec
596 ms
Click here to check amazing Restaurantstoronto content. Otherwise, check out these important facts you probably never knew about restaurantstoronto.com
The domain name restaurantstoronto.com is available for rent.
Visit restaurantstoronto.comWe analyzed Restaurantstoronto.com page load time and found that the first response time was 1.4 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Restaurantstoronto.com rating and web reputation
restaurantstoronto.com performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value0.9 s
100/100
25%
Value1.7 s
100/100
10%
Value190 ms
90/100
30%
Value0.202
61/100
15%
Value3.1 s
95/100
10%
1401 ms
36 ms
40 ms
41 ms
42 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 74% of them (66 requests) were addressed to the original Restaurantstoronto.com, 8% (7 requests) were made to Pagead2.googlesyndication.com and 6% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.9 sec) relates to the external source Static.addtoany.com.
Page size can be reduced by 289.1 kB (31%)
925.4 kB
636.3 kB
In fact, the total size of Restaurantstoronto.com main page is 925.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. 50% of websites need less resources to load. Images take 475.0 kB which makes up the majority of the site volume.
Potential reduce by 65.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. 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 65.4 kB or 80% of the original size.
Potential reduce by 22.8 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. Restaurantstoronto images are well optimized though.
Potential reduce by 145.7 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 145.7 kB or 49% of the original size.
Potential reduce by 55.1 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. Restaurantstoronto.com needs all CSS files to be minified and compressed as it can save up to 55.1 kB or 78% of the original size.
Number of requests can be reduced by 48 (55%)
87
39
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Restaurantstoronto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
restaurantstoronto.com
1401 ms
views.css
36 ms
node.css
40 ms
defaults.css
41 ms
system.css
42 ms
system-menus.css
41 ms
user.css
73 ms
advanced_profile.css
74 ms
content-module.css
73 ms
ctools.css
75 ms
extra_voting_forms_all.css
78 ms
filefield.css
79 ms
fivestar.css
105 ms
small.css
111 ms
lightbox.css
111 ms
panels.css
113 ms
fieldgroup.css
123 ms
twocol_stacked.css
122 ms
addtoany.css
137 ms
style.css
158 ms
jquery.js
168 ms
drupal.js
152 ms
extra_voting_forms.js
149 ms
fivestar.js
164 ms
lightbox.js
200 ms
panels.js
189 ms
s3Slider.js
189 ms
front-page.css
190 ms
blog.css
198 ms
adsbygoogle.js
5 ms
page.js
4945 ms
ga.js
35 ms
background.jpg
48 ms
rt_logo.png
84 ms
16.jpg
85 ms
onebit_44_small.png
79 ms
84 ms
onebit_50_small.png
78 ms
blog_small.png
84 ms
user.png
138 ms
calendar_day.png
137 ms
master-chef-canada.jpg
187 ms
arrow_next.png
162 ms
share_save_171_16.png
163 ms
good-restaurant-service.jpg
230 ms
peopleschoiceaward-toronto.jpg
213 ms
onebit_40_small.png
177 ms
logo_seven44.gif
209 ms
logo_casabarcelona.gif
192 ms
logo_folcos.gif
216 ms
logo_davidduncanhouse.gif
226 ms
logo_awshucks.gif
228 ms
logo_the-cure.gif
258 ms
tag-blue_small.png
249 ms
logo_hogtownpub.gif
255 ms
logo_sake_bar_kushi.gif
269 ms
logo_highland.gif
259 ms
logo_matahari.gif
267 ms
logo_top_gun_steak.gif
288 ms
logo_springrolls1800sheppard.gif
292 ms
back_right_div.gif
293 ms
onebit_10_small.png
298 ms
rt_temp.jpg
305 ms
small_star.png
304 ms
label_blue_new_small.png
319 ms
bullet.gif
330 ms
gears.png
330 ms
ca-pub-1642851502853519.js
67 ms
zrt_lookup.html
129 ms
show_ads_impl.js
59 ms
flag.png
310 ms
__utm.gif
63 ms
question.png
276 ms
ads
296 ms
osd.js
20 ms
ads
243 ms
8934335285066912619
50 ms
abg.js
53 ms
m_js_controller.js
60 ms
googlelogo_color_112x36dp.png
44 ms
s
49 ms
x_button_blue2.png
50 ms
favicon
44 ms
nessie_icon_tiamat_white.png
60 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
5 ms
activeview
12 ms
activeview
16 ms
sm13.html
49 ms
ga.js
38 ms
restaurantstoronto.com accessibility score
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
restaurantstoronto.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
restaurantstoronto.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Restaurantstoronto.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 Restaurantstoronto.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.
restaurantstoronto.com
Open Graph description is not detected on the main page of Restaurantstoronto. 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: