2.3 sec in total
215 ms
2 sec
97 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 215 ms and then it took 2.1 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
Value9.2 s
0/100
10%
Value45.5 s
0/100
25%
Value26.6 s
0/100
10%
Value5,900 ms
0/100
30%
Value0.023
100/100
15%
Value85.7 s
0/100
10%
215 ms
677 ms
125 ms
162 ms
104 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Locateottawa.ca, 62% (43 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 (677 ms) relates to the external source Properties.zoomprospector.com.
Page size can be reduced by 860.5 kB (81%)
1.1 MB
195.6 kB
In fact, the total size of Locateottawa.ca main page is 1.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. CSS take 733.7 kB which makes up the majority of the site volume.
Potential reduce by 80.4 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 80.4 kB or 78% 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 147.6 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 147.6 kB or 83% 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 (87%)
60
8
The browser has sent 60 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
215 ms
ottawa
677 ms
three.min.js
125 ms
gmaps-measuretool.umd.js
162 ms
markerclustererplus.min.js
104 ms
js
149 ms
react-image-gallery.css
119 ms
semantic.min.css
113 ms
zpe-icons.css
115 ms
main.css
135 ms
infobox.min.js
87 ms
locallayercontroller.js
86 ms
arcgis.js
329 ms
jquery.min.js
129 ms
html2canvas.min.js
140 ms
paper-full.min.js
155 ms
iframeshare.js
114 ms
pdfkit.standalone.js
156 ms
576c1bd08e06b60e.css
87 ms
polyfills-5cd94c89d3acac5f.js
102 ms
webpack-a146a8ef8f1e9d05.js
102 ms
framework-79bce4a3a540b080.js
112 ms
main-fa857edb36d92226.js
110 ms
_app-1c1200f68c76bdba.js
504 ms
8920-85e2a0e1d2880ecb.js
125 ms
2479-f0b0b45e5c22e41f.js
128 ms
5988-6f801c0eca69a879.js
128 ms
4919-3ac3c4ce361820ab.js
128 ms
227-9d657ded581e2a51.js
138 ms
5247-2ca2dadec5fa3ad3.js
140 ms
2709-bbffc8dcfda81441.js
143 ms
7001-3124de072c662fce.js
144 ms
2974-87bd528f95f6952c.js
145 ms
9542-998aee735536ea5d.js
145 ms
9941-6ec787162d15db0a.js
300 ms
3434-0ae3dbcce38b3acd.js
301 ms
2119-45c8210e02e482aa.js
303 ms
3908-a49850e2e4c2d66f.js
302 ms
6178-2961449a3d0827ad.js
306 ms
3255-370bcde5a89bf878.js
306 ms
1677-4eb9af576d9d2a67.js
306 ms
8425-6b5f57f787b49806.js
305 ms
1327-ed71c5c1cb5617d1.js
307 ms
826-a07f87433055317c.js
309 ms
9558-fbf4b6795fc6cdb9.js
310 ms
984-c7a6e15949fab546.js
310 ms
2521-18e7d2e33a68b696.js
309 ms
7472-369cc864c063bcee.js
312 ms
8457-718ee4d6bf9f37db.js
313 ms
polyfill.min.js
118 ms
4044-d093b7aa322ae7d2.js
314 ms
%5Bsst%5D-213483f274f19ebf.js
237 ms
_buildManifest.js
236 ms
_ssgManifest.js
356 ms
_middlewareManifest.js
224 ms
gen_204
131 ms
logoProperties.png
96 ms
gisp_logo.svg
78 ms
building.png
66 ms
site.png
68 ms
sllogo3.png
67 ms
lftracker_v1_ywVkO4X3G0p7Z6Bj.js
270 ms
icons.woff
10 ms
outline-icons.woff
9 ms
zpe-icons.woff
64 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff
135 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff
135 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
197 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff
198 ms
locateottawa.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-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
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
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: