5.7 sec in total
831 ms
3.9 sec
887 ms
Click here to check amazing Lee S Palace content for Canada. Otherwise, check out these important facts you probably never knew about leespalace.com
Lee's Palace is a rock concert hall located on the south side of Bloor Street West east of Lippincott Street in Toronto, Ontario, Canada.
Visit leespalace.comWe analyzed Leespalace.com page load time and found that the first response time was 831 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
leespalace.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value6.2 s
11/100
25%
Value5.3 s
57/100
10%
Value550 ms
53/100
30%
Value0.304
39/100
15%
Value7.2 s
51/100
10%
831 ms
30 ms
64 ms
101 ms
163 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Leespalace.com, 54% (65 requests) were made to Cdn.ticketfly.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 (837 ms) relates to the external source Cdn.ticketfly.com.
Page size can be reduced by 377.4 kB (22%)
1.7 MB
1.4 MB
In fact, the total size of Leespalace.com main page is 1.7 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.2 MB which makes up the majority of the site volume.
Potential reduce by 82.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. 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 82.9 kB or 83% of the original size.
Potential reduce by 19.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. Lee S Palace images are well optimized though.
Potential reduce by 209.0 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 209.0 kB or 62% of the original size.
Potential reduce by 65.7 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. Leespalace.com needs all CSS files to be minified and compressed as it can save up to 65.7 kB or 82% of the original size.
Number of requests can be reduced by 52 (45%)
115
63
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lee S Palace. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.leespalace.com
831 ms
gtm.js
30 ms
dc.js
64 ms
wp-emoji-release.min.js
101 ms
facebook-comments-hidewpcomments.css
163 ms
facebook-rsvp.css
165 ms
facebook-comments-widgets.css
180 ms
style.css
562 ms
css
46 ms
font-awesome.css
12 ms
style.css
186 ms
tfly-hide.css
189 ms
jquery.js
188 ms
jquery-migrate.min.js
189 ms
core.min.js
209 ms
widget.min.js
211 ms
mouse.min.js
212 ms
resizable.min.js
214 ms
draggable.min.js
215 ms
button.min.js
236 ms
position.min.js
235 ms
dialog.min.js
237 ms
tfly.js
241 ms
plugins.js
668 ms
script.js
662 ms
modernizr.min.js
38 ms
respond.js
39 ms
navigation.js
643 ms
skip-link-focus-fix.js
594 ms
wp-embed.min.js
265 ms
analytics.js
49 ms
__utm.gif
23 ms
__utm.gif
27 ms
__utm.gif
33 ms
collect
10 ms
collect
62 ms
no-image-medium.png
221 ms
logo.jpg
837 ms
25-atxl1.jpg
75 ms
99-atxl1.jpg
33 ms
43-atxl1.jpg
76 ms
81-emd.png
79 ms
11-emd.png
74 ms
99-emd.jpg
218 ms
95-atmd.jpg
219 ms
23-atmd.jpg
218 ms
85-atmd.jpg
217 ms
95-emd.jpg
226 ms
63-emd.jpg
224 ms
07-atmd.jpg
226 ms
83-atmd.jpg
226 ms
09-emd.jpg
227 ms
71-emd.jpg
232 ms
07-emd.jpg
226 ms
35-atmd.JPG
227 ms
11-atmd.jpg
228 ms
15-atmd.jpg
228 ms
85-emd.jpg
229 ms
33-emd.jpg
231 ms
35-atmd.png
231 ms
25-atmd.jpg
232 ms
47-atmd.jpg
233 ms
21-atmd.jpg
233 ms
37-emd.jpg
234 ms
21-atmd.jpg
234 ms
67-atmd.jpg
237 ms
99-atmd.jpg
237 ms
27-emd.jpg
238 ms
09-atmd.jpg
239 ms
29-atmd.JPG
239 ms
69-atmd.jpg
238 ms
43-atmd.jpg
239 ms
all.js
219 ms
widgets.js
47 ms
87-atmd.jpg
617 ms
6gvWg6msfvbhsU460ubKFqCWcynf_cDxXwCLxiixG1c.ttf
44 ms
lXoKq2PC8Z_S1wl-BwvrB-vvDin1pK8aKteLpeZ5c0A.ttf
44 ms
bH7276GfdCjMjApa_dkG6SZ2oysoEQEeKwjgmXLRnTc.ttf
45 ms
fontawesome-webfont.woff
41 ms
97-atmd.jpg
575 ms
63-atmd.jpg
570 ms
29-atmd.jpg
572 ms
35-atmd.jpg
566 ms
big-fat-burrito.png
540 ms
ticketfly.png
492 ms
weinland-creative.png
428 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
46 ms
149 ms
xd_arbiter.php
132 ms
xd_arbiter.php
280 ms
syndication
93 ms
444578190476853248
146 ms
nr-885.min.js
43 ms
ping
57 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
3 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
5 ms
c165d52f09
53 ms
PerlichPost-logo_normal.jpg
132 ms
Lee_s_Logo_colour_normal.JPG
158 ms
like_box.php
123 ms
410ucuAGgaJ.css
177 ms
tSbl8xBI27R.css
222 ms
q68gy-v_YMF.js
304 ms
FJmpeSpHpjS.js
375 ms
0wM5s1Khldu.js
300 ms
1bNoFZUdlYZ.js
299 ms
jot
22 ms
10245331_624749750933154_1572195939610749838_n.jpg
252 ms
180631_112850422123092_8203118_n.jpg
298 ms
10271550_10156534904790375_8561363603262060275_n.jpg
345 ms
12108812_10153234986793131_8484132061927917164_n.jpg
371 ms
12376614_10156478744390192_5429189014958814622_n.jpg
557 ms
576971_10151718277035024_47727452_n.jpg
372 ms
426958_485280441500806_1556833633_n.jpg
403 ms
11169894_1418127101839311_2119493693039137886_n.jpg
370 ms
12729141_1017414611650965_1071794345281993003_n.jpg
395 ms
wL6VQj7Ab77.png
50 ms
s7jcwEQH7Sx.png
53 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
81 ms
leespalace.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Links do not have a discernible name
leespalace.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
leespalace.com SEO score
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 uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leespalace.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 Leespalace.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.
leespalace.com
Open Graph description is not detected on the main page of Lee S Palace. 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: