2 sec in total
154 ms
1.8 sec
64 ms
Welcome to locateottawa.ca homepage info - get ready to check Locate Ottawa best content right away, or after learning these important things about locateottawa.ca
Search for available commercial, industrial, office, retail or warehouse properties. Make informed site selection decisions by generating site-specific reports on demographics, workforce, competitors ...
Visit locateottawa.caWe analyzed Locateottawa.ca page load time and found that the first response time was 154 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
locateottawa.ca performance score
name
value
score
weighting
Value12.8 s
0/100
10%
Value49.0 s
0/100
25%
Value21.2 s
0/100
10%
Value2,900 ms
3/100
30%
Value0.023
100/100
15%
Value48.7 s
0/100
10%
154 ms
912 ms
50 ms
62 ms
45 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Locateottawa.ca, 66% (45 requests) were made to Properties.zoomprospector.com and 10% (7 requests) were made to D1hd8317vngzg3.cloudfront.net. The less responsive or slowest element that took the longest time to load (912 ms) relates to the external source Properties.zoomprospector.com.
Page size can be reduced by 4.7 MB (80%)
5.9 MB
1.2 MB
In fact, the total size of Locateottawa.ca main page is 5.9 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 5.0 MB which makes up the majority of the site volume.
Potential reduce by 88.1 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 88.1 kB or 79% of the original size.
Potential reduce by 4.6 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, Locate Ottawa needs image optimization as it can save up to 4.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.0 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 4.0 MB or 80% of the original size.
Potential reduce by 627.9 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. Locateottawa.ca needs all CSS files to be minified and compressed as it can save up to 627.9 kB or 86% of the original size.
Number of requests can be reduced by 52 (88%)
59
7
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Locate Ottawa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
locateottawa.ca
154 ms
ottawa
912 ms
three.min.js
50 ms
gmaps-measuretool.umd.js
62 ms
markerclustererplus.min.js
45 ms
js
92 ms
react-image-gallery.css
47 ms
semantic.min.css
52 ms
zpe-icons.css
46 ms
main.css
52 ms
infobox.min.js
30 ms
locallayercontroller.js
37 ms
arcgis.js
54 ms
jquery.min.js
55 ms
html2canvas.min.js
66 ms
paper-full.min.js
51 ms
iframeshare.js
45 ms
pdfkit.standalone.js
59 ms
js
170 ms
990b545e0d6bf535.css
189 ms
polyfills-0d1b80a048d4787e.js
232 ms
webpack-a146a8ef8f1e9d05.js
231 ms
framework-79bce4a3a540b080.js
329 ms
main-0bb5a2737401a5ce.js
326 ms
_app-9c10d1f734ac1bb7.js
689 ms
2cca2479-aad4c5eeb17d6215.js
326 ms
7384-e534c14dfddeebfe.js
375 ms
6089-8aef55a87928fc1e.js
375 ms
1465-fcadd3e9cd8ebeb7.js
376 ms
2479-456a5901c43ccf08.js
410 ms
7156-53e8f817e21ba830.js
409 ms
3690-456f2edfad7b5101.js
410 ms
5247-2ca2dadec5fa3ad3.js
410 ms
5019-b0a68f977c7a57cf.js
436 ms
5536-29d8546243473c9c.js
449 ms
9542-998aee735536ea5d.js
437 ms
2974-87bd528f95f6952c.js
438 ms
3749-ba57c4b0e47845de.js
472 ms
9941-c1049697985c3b35.js
464 ms
9565-13140091c289cb99.js
472 ms
5330-1641018b27dfd034.js
479 ms
3930-1a21071ed08f9d57.js
484 ms
9080-4cfb77a8acd5267b.js
510 ms
9626-375a7a8cdb628f68.js
514 ms
1818-faa9fd388a4feb2b.js
510 ms
4312-750dfa468d386f72.js
518 ms
1852-46c93e519caec1fb.js
528 ms
4214-227396fd33b465fc.js
552 ms
4514-31ca15c6dfa89220.js
550 ms
5909-65710a8ebf4fccf7.js
530 ms
1635-a28e8f2096d457b9.js
523 ms
6739-96335810bab1a7bd.js
536 ms
%5Bsst%5D-21a9ada4837fcdf5.js
533 ms
_buildManifest.js
534 ms
_ssgManifest.js
527 ms
lftracker_v1_lAxoEaKqV0d7OYGd.js
450 ms
logoProperties.png
34 ms
gisp_logo.svg
33 ms
sllogo3.png
33 ms
building.png
33 ms
site.png
33 ms
icons.woff
234 ms
outline-icons.woff
254 ms
zpe-icons.woff
24 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff
47 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff
48 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
79 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff
80 ms
locateottawa.ca 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
[id] attributes on active, focusable elements 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
locateottawa.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
locateottawa.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locateottawa.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 Locateottawa.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.
locateottawa.ca
Open Graph description is not detected on the main page of Locate Ottawa. 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: