4.8 sec in total
123 ms
3.8 sec
905 ms
Visit toronto-lime.com now to see the best up-to-date Torontolime content and also check out these interesting facts you probably never knew about toronto-lime.com
Torontolime is your best source for Toronto Events
Visit toronto-lime.comWe analyzed Toronto-lime.com page load time and found that the first response time was 123 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
toronto-lime.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.623
10/100
15%
Value0
0/100
10%
123 ms
244 ms
31 ms
59 ms
60 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Toronto-lime.com, 58% (76 requests) were made to Torontolime.com and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (861 ms) relates to the external source Chat.livechatinc.net.
Page size can be reduced by 1.1 MB (33%)
3.2 MB
2.1 MB
In fact, the total size of Toronto-lime.com main page is 3.2 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. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 5.9 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 1.4 kB, which is 18% 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 5.9 kB or 76% of the original size.
Potential reduce by 42.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. Torontolime images are well optimized though.
Potential reduce by 691.4 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 691.4 kB or 78% of the original size.
Potential reduce by 325.3 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. Toronto-lime.com needs all CSS files to be minified and compressed as it can save up to 325.3 kB or 86% of the original size.
Number of requests can be reduced by 71 (57%)
124
53
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Torontolime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
toronto-lime.com
123 ms
www.torontolime.com
244 ms
player.css
31 ms
jquery.jscrollpane.css
59 ms
jquery.lightbox.css
60 ms
jquery.min.js
38 ms
jcarousel.js
115 ms
swfobject.js
123 ms
jquery.jscrollpane.min.js
127 ms
jquery.mousewheel.js
133 ms
jquery.lightbox.min.js
135 ms
mediacontroller.js
133 ms
torontolime.js
140 ms
ga.js
80 ms
home
153 ms
player-play-2.png
62 ms
player-pause-2.png
64 ms
player-prev-2.png
62 ms
player-next-2.png
88 ms
player-progress-bkg.png
63 ms
player-progress-loaded-bkg.png
89 ms
player-progress-bar-bkg.png
92 ms
player-volume.png
94 ms
volume-bkg.jpg
92 ms
volume-bkg-active.jpg
95 ms
volume-slider.png
95 ms
player-repeat.png
101 ms
player-repeat-active.png
99 ms
player-shuffle.png
101 ms
player-shuffle-active.png
103 ms
player-size.png
106 ms
player-size-active.png
107 ms
jquery-lightbox-theme.gif
109 ms
__utm.gif
48 ms
reset.css
56 ms
icons.css
60 ms
icons.css
63 ms
layout.css
105 ms
dcsns_wall.css
71 ms
desktop.css
77 ms
tablet.css
82 ms
mobile.css
95 ms
chosen.css
129 ms
flexslider.css
131 ms
modernizr-2.6.2.min.js
137 ms
init.js
186 ms
ajax.js
189 ms
form.js
190 ms
calendar.js
194 ms
element.js
196 ms
events.js
197 ms
site.js
198 ms
site.js
199 ms
jquery-1.11.0.js
214 ms
chosen.jquery.js
200 ms
buttons.js
39 ms
jquery.flexslider.js
198 ms
functions.js
197 ms
background-2014.jpg
312 ms
background_background-2014.jpg
273 ms
top-bar.png
71 ms
logo-2014.png
68 ms
logo-2014-mobile.png
71 ms
big-wrap2.png
69 ms
hero_1000_100ARIESFRONT2_2.jpg
240 ms
hero_ticket_slides.png
260 ms
tile_buttons%20media2.jpg
135 ms
tile_buttons%20photos.jpg
197 ms
tile_buttons%20events.jpg
194 ms
tile_buttons%20rumshop.jpg
243 ms
150_first-wine-2016.jpg
457 ms
150_THECURE_Bandit2015_1400x1400.jpg
211 ms
video-hover.png
239 ms
150_DBANDIT_VIDMIX-2015_1400X1400.jpg
264 ms
150_Photography%20By%20Teeography%20_-206.jpg
266 ms
150_LUXY0014.jpg
269 ms
widgets.js
81 ms
itcfranklingothicltmediumcondensed.woff
214 ms
gothmbcd-webfont.woff
222 ms
fontawesome-webfont.woff
223 ms
fontawesome-webfont.woff
246 ms
all.js
272 ms
icon-sharethis.png
240 ms
buttontype.cgi
861 ms
135 ms
xd_arbiter.php
217 ms
xd_arbiter.php
426 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
169 ms
ping
130 ms
getAllAppDefault.esi
25 ms
__utm.gif
18 ms
getSegment.php
43 ms
checkOAuth.esi
37 ms
syndication
129 ms
331490713067978753
203 ms
t.dhj
34 ms
like_box.php
254 ms
t.dhj
18 ms
cm
23 ms
s-3271.xgi
21 ms
hbpix
59 ms
19 ms
24 ms
xrefid.xgi
33 ms
pixel
21 ms
pixel
18 ms
2981
28 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
52 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
90 ms
ebiMDO3r-8l.css
302 ms
wakJkBioHgT.css
371 ms
FAHeNGXgPup.js
507 ms
FJmpeSpHpjS.js
640 ms
0wM5s1Khldu.js
530 ms
1bNoFZUdlYZ.js
529 ms
up646osdxbnxredgx17j_normal.jpeg
115 ms
jot
27 ms
10372275_664884893598961_8095409659674100987_n.jpg
301 ms
10366231_663498067070977_7039606866592671125_n.jpg
364 ms
12316157_101291933585841_9021101607058101757_n.jpg
433 ms
12189761_10153625788701125_5601845046650393089_n.jpg
498 ms
1379841_10150004552801901_469209496895221757_n.jpg
497 ms
10985463_871887679562001_8406295538964323584_n.jpg
496 ms
12745502_978156302265173_1495749009562021720_n.jpg
498 ms
wL6VQj7Ab77.png
126 ms
s7jcwEQH7Sx.png
124 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
45 ms
buttons.ab966a004186897711de4a5ed256c924.css
45 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
17 ms
st.1188278743c14064d5e8ae56c8ada29c.js
24 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
136 ms
toronto-lime.com accessibility score
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
toronto-lime.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
toronto-lime.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toronto-lime.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 Toronto-lime.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.
toronto-lime.com
Open Graph description is not detected on the main page of Torontolime. 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: