3.8 sec in total
198 ms
3 sec
546 ms
Welcome to lakeshorehonda.com homepage info - get ready to check Lakeshore Honda best content for Canada right away, or after learning these important things about lakeshorehonda.com
At Honda Queensway, check out our new and pre-owned Honda vehicles today. We are your number one Honda dealership for service in Toronto as well.
Visit lakeshorehonda.comWe analyzed Lakeshorehonda.com page load time and found that the first response time was 198 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lakeshorehonda.com performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value42.5 s
0/100
25%
Value27.4 s
0/100
10%
Value17,350 ms
0/100
30%
Value0.292
41/100
15%
Value55.7 s
0/100
10%
198 ms
917 ms
95 ms
101 ms
143 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lakeshorehonda.com, 18% (19 requests) were made to Static.xx.fbcdn.net and 17% (18 requests) were made to Widgets-cdn.sm360.ca. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cdn.icomoon.io.
Page size can be reduced by 486.4 kB (14%)
3.4 MB
2.9 MB
In fact, the total size of Lakeshorehonda.com main page is 3.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. Only a small number of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 425.8 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 192.0 kB, which is 41% 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 425.8 kB or 91% of the original size.
Potential reduce by 9.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. Lakeshore Honda images are well optimized though.
Potential reduce by 19.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. This website has mostly compressed JavaScripts.
Potential reduce by 32.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. Lakeshorehonda.com needs all CSS files to be minified and compressed as it can save up to 32.3 kB or 19% of the original size.
Number of requests can be reduced by 73 (75%)
97
24
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lakeshore Honda. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
lakeshorehonda.com
198 ms
en
917 ms
core-ux.min.css
95 ms
main.css
101 ms
style-svg.css
143 ms
style.css
165 ms
honda.min.css
81 ms
honda.css
111 ms
swiper-bundle.min.css
80 ms
jquery-1.12.4.min.js
73 ms
jquery-migrate-1.2.1.min.js
97 ms
jquery-ui.min.js
120 ms
jquery.cookie.js
80 ms
jquery.sm360.cookieArray.js
79 ms
compareTool.js
84 ms
core-ux.min.js
93 ms
enterprise.js
115 ms
reset.css
88 ms
theme
121 ms
0000-widgets.min.css
92 ms
react.production.min.js
92 ms
react-dom.production.min.js
111 ms
moment.min.js
114 ms
en-ca.js
120 ms
immutable.min.js
116 ms
raven.min.js
118 ms
axios.min.js
92 ms
lodash.min.js
122 ms
widget-16.82.0.min.js
95 ms
widget-16.82.0.min.js
92 ms
widget-16.82.0.min.css
94 ms
widget-16.82.0.min.js
101 ms
widget-16.82.0.min.css
94 ms
widget-16.82.0.min.js
97 ms
widget-16.82.0.min.js
102 ms
widget-16.82.0.min.css
101 ms
widget-16.82.0.min.js
109 ms
widget-16.82.0.min.css
100 ms
widget-16.82.0.min.js
111 ms
widget-16.82.0.min.css
108 ms
widget-16.82.0.min.js
110 ms
widget-16.82.0.min.css
110 ms
gtm.js
184 ms
gtm.js
314 ms
recaptcha__en.js
273 ms
transaction-bar-garage-icon1700671187832.svg
245 ms
transaction-bar-tradein-icon1700671211919.svg
246 ms
transaction-bar-finance-icon1700671179813.svg
248 ms
2024-06-honda-queensway-1200x1200-logo-1-1719593895973.png
244 ms
HelveticaNeue.woff
197 ms
Verdana.woff
67 ms
2024-09-honda-desktop-768x500-promo-event-en1725565266471.jpg
174 ms
2024-09-honda-desktop-768x500-promo-crv-en1725565402285.jpg
172 ms
2023-12-honda-queensway-header-mobile-768x500-honda-pilot-20241702068064549.jpg
174 ms
2023-12-honda-queensway-header-mobile-768x500-honda-accord-20241702067918792.jpg
175 ms
Verdana-Bold.woff
51 ms
showroom.ttf
51 ms
showroom.ttf
51 ms
National-Regular.woff
93 ms
HelveticaNeue-Bold.woff
489 ms
2024_honda_hr-v_sport-b_001_nh830m.png
98 ms
widget-16.75.0.min.js
76 ms
widget-16.75.0.min.css
66 ms
signals.js
113 ms
a97f96c7-6046-48c7-88ba-654e412dc408
355 ms
2024_honda_cr-v_lx-b-awd_001_nh830m.png
59 ms
2024_honda_odyssey_ex-l_001_nh797m.png
59 ms
2024_honda_hr-v_sport-b_032_nh830m.png
61 ms
2024_honda_cr-v_lx-b-awd_032_nh830m.png
62 ms
2024_honda_odyssey_ex-l_032_nh797m.png
61 ms
tradein-teaser-icon1700671134163.png
60 ms
CBB-square-2022.png
60 ms
core-ux.min.js
59 ms
svgxuse.js
1226 ms
main.min.js
60 ms
foundation.min.js
58 ms
swiper-bundle.min.js
60 ms
app.js
60 ms
urlTracker.js
57 ms
en-dark.png
56 ms
HelveticaNeue-Medium.woff
157 ms
css
39 ms
sdk.js
72 ms
sdk.js
51 ms
page.php
218 ms
cherry-popper.min.js
22 ms
cherries
20 ms
YSVNzQMiK3c.css
23 ms
erDxurAZPYM.css
28 ms
SHRLQdjpXb9.css
24 ms
gXblFixtPJ3.js
34 ms
FsgTKAP125G.js
31 ms
pLoSlJD7y1F.js
30 ms
o1ndYS2og_B.js
31 ms
Glud--w-qOK.js
31 ms
WvbRbK9sYiL.js
32 ms
p55HfXW__mM.js
32 ms
ALTQi95mOyD.js
62 ms
r5HcOUY3OX6.js
64 ms
DtR0X5vxkLl.js
70 ms
8IAOdJiZGNE.js
70 ms
yhMLxgtMNUo.js
82 ms
daRG11v-d-4.js
81 ms
HzxD9aAXSyD.js
81 ms
359801781_651771446970563_2775919219442785049_n.jpg
209 ms
Z5pveUhzVtX.js
8 ms
218763535_4820243484656976_5696161436226792795_n.png
31 ms
UXtr_j2Fwe-.png
5 ms
lakeshorehonda.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
lakeshorehonda.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lakeshorehonda.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lakeshorehonda.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 Lakeshorehonda.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.
lakeshorehonda.com
Open Graph data is detected on the main page of Lakeshore Honda. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: