7.6 sec in total
2 sec
5.5 sec
88 ms
Visit onsiteconstruction.ca now to see the best up-to-date O N Site Construction content and also check out these interesting facts you probably never knew about onsiteconstruction.ca
O.N. Site Construction Inc. is an Ontario based construction company that has been in operation in Canada since 2005.
Visit onsiteconstruction.caWe analyzed Onsiteconstruction.ca page load time and found that the first response time was 2 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
onsiteconstruction.ca performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value5.4 s
21/100
25%
Value12.2 s
3/100
10%
Value680 ms
43/100
30%
Value0.181
67/100
15%
Value10.0 s
26/100
10%
1973 ms
20 ms
38 ms
78 ms
95 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 75% of them (120 requests) were addressed to the original Onsiteconstruction.ca, 21% (34 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Onsiteconstruction.ca.
Page size can be reduced by 2.4 MB (77%)
3.1 MB
701.0 kB
In fact, the total size of Onsiteconstruction.ca main page is 3.1 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. 70% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 62.6 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 62.6 kB or 80% of the original size.
Potential reduce by 5.1 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. Obviously, O N Site Construction needs image optimization as it can save up to 5.1 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.2 MB
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 1.2 MB or 70% of the original size.
Potential reduce by 1.1 MB
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. Onsiteconstruction.ca needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 88% of the original size.
Number of requests can be reduced by 115 (93%)
123
8
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O N Site Construction. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 110 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
onsiteconstruction.ca
1973 ms
wp-emoji-release.min.js
20 ms
classic-themes.min.css
38 ms
rs6.css
78 ms
style.min.css
95 ms
style.css
51 ms
background-extend.css
51 ms
fcab38f5ecd22ec84b0b756725b8bc61.min.css
148 ms
jquery.min.js
68 ms
jquery-migrate.min.js
68 ms
rbtools.min.js
110 ms
rs6.min.js
101 ms
wpgmza_data.js
87 ms
js
60 ms
css
29 ms
background-extend.js
97 ms
Chart.js
267 ms
fusion-chart.js
110 ms
modernizr.js
109 ms
fusion-column-bg-image.js
116 ms
cssua.js
125 ms
jquery.waypoints.js
128 ms
fusion-waypoints.js
127 ms
fusion-animations.js
133 ms
fusion-equal-heights.js
142 ms
fusion-column.js
266 ms
jquery.fade.js
265 ms
jquery.requestAnimationFrame.js
265 ms
fusion-parallax.js
266 ms
jquery.fitvids.js
267 ms
fusion-video-general.js
267 ms
fusion-video-bg.js
269 ms
jquery.sticky-kit.js
268 ms
fusion-container.js
268 ms
fusion-content-boxes.js
269 ms
jquery.countdown.js
270 ms
fusion-countdown.js
270 ms
jquery.countTo.js
271 ms
jquery.appear.js
269 ms
fusion-counters-box.js
258 ms
jquery.easyPieChart.js
243 ms
fusion-counters-circle.js
228 ms
fusion-flip-boxes.js
228 ms
isotope.js
213 ms
packery.js
211 ms
jquery.ilightbox.js
201 ms
jquery.mousewheel.js
195 ms
fusion-lightbox.js
185 ms
imagesLoaded.js
185 ms
fusion-gallery.js
182 ms
jquery.fusion_maps.js
174 ms
fusion-google-map.js
174 ms
jquery.event.move.js
174 ms
fusion-image-before-after.js
169 ms
lottie.js
202 ms
fusion-lottie.js
155 ms
fusion-menu.js
156 ms
bootstrap.modal.js
151 ms
fusion-modal.js
144 ms
gtm.js
55 ms
fusion-progress.js
57 ms
fusion-recent-posts.js
56 ms
fusion-syntax-highlighter.js
55 ms
bootstrap.transition.js
55 ms
bootstrap.tab.js
56 ms
fusion-tabs.js
58 ms
jquery.cycle.js
57 ms
fusion-testimonials.js
55 ms
jquery.textillate.js
55 ms
fusion-title.js
55 ms
bootstrap.collapse.js
105 ms
fusion-toggles.js
104 ms
avada-portfolio.js
104 ms
jquery.infinitescroll.js
102 ms
avada-faqs.js
104 ms
flatpickr.js
102 ms
fusion-form.js
215 ms
vimeoPlayer.js
215 ms
fusion-video.js
217 ms
jquery.hoverintent.js
214 ms
fusion-vertical-menu-widget.js
213 ms
fusion.js
215 ms
lazysizes.js
283 ms
bootstrap.tooltip.js
285 ms
bootstrap.popover.js
283 ms
jquery.carouFredSel.js
284 ms
jquery.easing.js
283 ms
jquery.flexslider.js
283 ms
jquery.hoverflow.js
286 ms
jquery.placeholder.js
288 ms
jquery.touchSwipe.js
287 ms
fusion-alert.js
286 ms
fusion-carousel.js
285 ms
fusion-flexslider.js
285 ms
fusion-popover.js
285 ms
analytics.js
82 ms
o-0IIpQlx3QUlC5A4PNr5TRGSf6M7Q.woff
81 ms
o-0IIpQlx3QUlC5A4PNr6zRGSf6M7VBj.woff
198 ms
o-0IIpQlx3QUlC5A4PNr6jRGSf6M7VBj.woff
269 ms
o-0IIpQlx3QUlC5A4PNr5jRGSf6M7VBj.woff
271 ms
o-0IIpQlx3QUlC5A4PNr6TRGSf6M7VBj.woff
270 ms
o-0IIpQlx3QUlC5A4PNr5DRGSf6M7VBj.woff
275 ms
o-0IIpQlx3QUlC5A4PNr4TRGSf6M7VBj.woff
272 ms
o-0IIpQlx3QUlC5A4PNr6DRGSf6M7VBj.woff
270 ms
o-0NIpQlx3QUlC5A4PNjXhFVZNyHx2pqPA.woff
269 ms
o-0NIpQlx3QUlC5A4PNjXhFVatyHx2pqPIif.woff
276 ms
o-0NIpQlx3QUlC5A4PNjXhFVa9yHx2pqPIif.woff
277 ms
o-0NIpQlx3QUlC5A4PNjXhFVZ9yHx2pqPIif.woff
278 ms
o-0NIpQlx3QUlC5A4PNjXhFVaNyHx2pqPIif.woff
278 ms
o-0NIpQlx3QUlC5A4PNjXhFVZdyHx2pqPIif.woff
328 ms
o-0NIpQlx3QUlC5A4PNjXhFVYNyHx2pqPIif.woff
278 ms
o-0NIpQlx3QUlC5A4PNjXhFVadyHx2pqPIif.woff
328 ms
Yq6R-LCAWCX3-6Ky7FAFrOF6lDouQb4.woff
328 ms
Yq6R-LCAWCX3-6Ky7FAFrO96lDouQb5-6g.woff
405 ms
fusion-tooltip.js
254 ms
fusion-sharing-box.js
251 ms
fusion-blog.js
250 ms
fusion-button.js
251 ms
fusion-general-global.js
248 ms
avada-header.js
294 ms
avada-menu.js
295 ms
fusion-scroll-to-anchor.js
292 ms
fusion-responsive-typography.js
293 ms
avada-skip-link-focus-fix.js
297 ms
js
152 ms
bootstrap.scrollspy.js
278 ms
avada-comments.js
252 ms
avada-general-footer.js
253 ms
avada-quantity.js
252 ms
avada-scrollspy.js
254 ms
avada-select.js
253 ms
avada-sidebars.js
254 ms
collect
120 ms
avada-tabs-widget.js
142 ms
avada-to-top.js
143 ms
avada-drop-down.js
139 ms
avada-live-search.js
140 ms
logo.png
146 ms
transparent.png
146 ms
collect
153 ms
logo.png
129 ms
logo-SMALL.png
1529 ms
icomoon.woff
21 ms
revicons.woff
23 ms
o-0OIpQlx3QUlC5A4PNr4ARCQ_-u72Bi.woff
23 ms
o-0OIpQlx3QUlC5A4PNr4ARMQ_-u72BiBLE.woff
82 ms
o-0OIpQlx3QUlC5A4PNr4ARNQ_-u72BiBLE.woff
76 ms
o-0OIpQlx3QUlC5A4PNr4ARBQ_-u72BiBLE.woff
95 ms
o-0OIpQlx3QUlC5A4PNr4AROQ_-u72BiBLE.woff
177 ms
o-0OIpQlx3QUlC5A4PNr4ARDQ_-u72BiBLE.woff
33 ms
o-0OIpQlx3QUlC5A4PNr4ARGQ_-u72BiBLE.woff
186 ms
o-0OIpQlx3QUlC5A4PNr4ARPQ_-u72BiBLE.woff
61 ms
o-0TIpQlx3QUlC5A4PNr4Az5ZuyDzWtIPrie.woff
91 ms
o-0TIpQlx3QUlC5A4PNr4Az5ZuyNzWtIPriezag.woff
163 ms
o-0TIpQlx3QUlC5A4PNr4Az5ZuyMzWtIPriezag.woff
110 ms
o-0TIpQlx3QUlC5A4PNr4Az5ZuyAzWtIPriezag.woff
121 ms
o-0TIpQlx3QUlC5A4PNr4Az5ZuyPzWtIPriezag.woff
125 ms
o-0TIpQlx3QUlC5A4PNr4Az5ZuyCzWtIPriezag.woff
138 ms
o-0TIpQlx3QUlC5A4PNr4Az5ZuyHzWtIPriezag.woff
150 ms
o-0TIpQlx3QUlC5A4PNr4Az5ZuyOzWtIPriezag.woff
165 ms
logo@2x.png
32 ms
onsiteconstruction.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
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
onsiteconstruction.ca 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
onsiteconstruction.ca SEO score
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 Onsiteconstruction.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 Onsiteconstruction.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.
onsiteconstruction.ca
Open Graph description is not detected on the main page of O N Site Construction. 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: