5.9 sec in total
1.9 sec
3.7 sec
219 ms
Welcome to limestone.on.ca homepage info - get ready to check Limestone On best content for Canada right away, or after learning these important things about limestone.on.ca
Visit limestone.on.caWe analyzed Limestone.on.ca page load time and found that the first response time was 1.9 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
limestone.on.ca performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value27.4 s
0/100
25%
Value9.8 s
10/100
10%
Value5,100 ms
0/100
30%
Value0.394
26/100
15%
Value23.7 s
1/100
10%
1932 ms
78 ms
82 ms
83 ms
80 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 91% of them (93 requests) were addressed to the original Limestone.on.ca, 4% (4 requests) were made to Translate.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Limestone.on.ca.
Page size can be reduced by 213.2 kB (22%)
955.6 kB
742.4 kB
In fact, the total size of Limestone.on.ca main page is 955.6 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. 45% of websites need less resources to load. Images take 623.7 kB which makes up the majority of the site volume.
Potential reduce by 142.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 142.5 kB or 84% of the original size.
Potential reduce by 21.5 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. Limestone On images are well optimized though.
Potential reduce by 804 B
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 48.4 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. Limestone.on.ca needs all CSS files to be minified and compressed as it can save up to 48.4 kB or 77% of the original size.
Number of requests can be reduced by 26 (26%)
100
74
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Limestone On. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
limestone.on.ca
1932 ms
reset-fonts-grids.css
78 ms
menu.css
82 ms
Searchbutton.css
83 ms
google_style.css
80 ms
featuredPlayer2.css
83 ms
mu_doc_rotate.css
130 ms
RWDMashup_PreviewContentSlider.css
123 ms
nyroModal.css
123 ms
colorbox.css
128 ms
jplist.css
125 ms
default.css
113 ms
flick.css
212 ms
RWDinsert_CSS.css
170 ms
RWDinsert_CSS.css
167 ms
RWDScroll.js
166 ms
anarchy.js
195 ms
jquery-1.7.2.min.js
253 ms
yahoo-dom-event.js
232 ms
container_core.js
311 ms
menu.js
271 ms
img_Fadein_Slideshow.js
227 ms
featuredPlayer2.js
226 ms
RWDMashup_PreviewContentSlider.js
275 ms
jquery.metadata.js
274 ms
jquery.media.js
277 ms
jquery.hoverIntent.js
285 ms
jquery.cycle.all.js
326 ms
jquery.corner.js
332 ms
jquery.pause.js
329 ms
jquery.marquee.min.js
329 ms
RWDjs.js
330 ms
mbMenu.js
376 ms
jquery.nyroModal.custom.js
378 ms
jquery.colorbox-min.js
376 ms
jplist.min.js
377 ms
element.js
49 ms
Override_RWD_Default_Style.css
332 ms
Override_RWD_Default_Style.css
329 ms
RWDModal_Call.js
370 ms
ijp-0.6.js
371 ms
rrecur-parser.js
371 ms
jquery.ui.core.js
368 ms
jquery.ui.widget.js
336 ms
jquery.ui.datepicker.js
341 ms
overlib.js
368 ms
divexpand.gif
45 ms
divcollapse.gif
47 ms
1px_trans.gif
50 ms
page_bg.jpg
51 ms
glob_hl_lft.jpg
49 ms
pixel.gif
68 ms
icon_twitter.png
74 ms
icon_pinterest.png
93 ms
icon_YouTube.png
94 ms
glob_hl_rt.jpg
95 ms
bnr_lft.jpg
165 ms
bnr_rt.jpg
152 ms
Hl_lft.jpg
109 ms
HP_header_bg.jpg
145 ms
LinL-Roots-Grow-Blossoms.jpg
249 ms
LIL-underground-railroad.jpg
248 ms
LIL-zombie-geogrpahy.gif
175 ms
video_ad.jpg
248 ms
S10FC7723-10FC80E1
369 ms
S10FC80D9-10FC80E0
374 ms
S10FC04E9-10FC80DF
367 ms
S10FC48E1-10FC80DE
372 ms
S10FB6EED-10FC80DD
366 ms
0
283 ms
0E84C7EA-00870BC8
588 ms
0E84C7EA-00870BC8
651 ms
0E84C7EA-00870BC8
656 ms
0E84C7EA-00870BC8
652 ms
0E84C7EA-00870BC8
655 ms
0E84C7EA-00870BC8
656 ms
3232015_121539_1.jpg
658 ms
PARC_Button.jpg
779 ms
0E2D0D99-00870BC8
880 ms
0E2D0D99-00870BC8
862 ms
glob_hl_bg.jpg
670 ms
translateelement.css
60 ms
main.js
83 ms
g_search2.png
598 ms
Hl_bg.jpg
589 ms
placeHolder.html
590 ms
S10FC5E80-10FC5E89
758 ms
S10FC4923-10FC5BE4
755 ms
S10F98755-10FC5750
760 ms
element_main.js
41 ms
ga.js
44 ms
__utm.gif
11 ms
overlay.png
655 ms
translate_24dp.png
52 ms
l
38 ms
googlelogo_color_42x16dp.png
56 ms
S10FC4923-10FC5BE4
148 ms
S10FC5E80-10FC5E89
145 ms
slideshowconfig
215 ms
S10F98755-10FC5750
141 ms
dwn_arrow_sm.gif
53 ms
slideshow_bg.jpg
252 ms
limestone.on.ca 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
[aria-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
limestone.on.ca 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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
limestone.on.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Limestone.on.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 Limestone.on.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.
limestone.on.ca
Open Graph description is not detected on the main page of Limestone On. 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: