4.3 sec in total
555 ms
3.6 sec
100 ms
Visit maps.edmonton.ca now to see the best up-to-date Maps Edmonton content for Canada and also check out these interesting facts you probably never knew about maps.edmonton.ca
Visit maps.edmonton.caWe analyzed Maps.edmonton.ca page load time and found that the first response time was 555 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
maps.edmonton.ca performance score
name
value
score
weighting
Value21.7 s
0/100
10%
Value22.3 s
0/100
25%
Value21.7 s
0/100
10%
Value1,210 ms
20/100
30%
Value0.517
15/100
15%
Value23.4 s
1/100
10%
555 ms
123 ms
417 ms
194 ms
918 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 95% of them (59 requests) were addressed to the original Maps.edmonton.ca, 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Maps.edmonton.ca.
Page size can be reduced by 2.6 MB (74%)
3.6 MB
943.2 kB
In fact, the total size of Maps.edmonton.ca main page is 3.6 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. 40% of websites need less resources to load. Javascripts take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 18.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. This page needs HTML code to be minified as it can gain 3.3 kB, which is 15% 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 18.1 kB or 79% of the original size.
Potential reduce by 7.2 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. Maps Edmonton images are well optimized though.
Potential reduce by 2.3 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 2.3 MB or 74% of the original size.
Potential reduce by 292.6 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. Maps.edmonton.ca needs all CSS files to be minified and compressed as it can save up to 292.6 kB or 88% of the original size.
Number of requests can be reduced by 49 (80%)
61
12
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maps Edmonton. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
maps.edmonton.ca
555 ms
landing.css
123 ms
layout.css
417 ms
typography.css
194 ms
slimGadget-all.js
918 ms
slimGadget-all.css
347 ms
anonsecurity.ashx
189 ms
slim.AddressLookupAppManager.js
199 ms
slim.AddressRangeLookupAppManager.js
246 ms
slim.AdminBoundariesAppManager.js
255 ms
slim.AssessmentParcelAppManager.js
268 ms
slim.BusStopsAppManager.js
303 ms
slim.WMSAppManager.js
318 ms
slim.TransitRouteAppManager.js
336 ms
slim.DevelopmentApplicationsAppManager.js
360 ms
slim.RedlineAppManager.js
380 ms
slim.DrivingDirectionsAppManager.js
404 ms
slim.IntersectionsAppManager.js
421 ms
slim.LandApplicationsAppManager.js
421 ms
slim.LandSalesAppManager.js
441 ms
slim.LegalDescriptionLookupAppManager.js
417 ms
slim.MunicipalAddressLookupAppManager.js
413 ms
slim.NamedLocationAppManager.js
425 ms
slim.NeighbourhoodAppManager.js
416 ms
slim.PostalCodesAppManager.js
461 ms
slim.SchoolsAppManager.js
469 ms
slim.SitesOfInterestAppManager.js
484 ms
slim.WhereToVoteAppManager.js
472 ms
toc.js
491 ms
help.css
522 ms
bg_headerPopup2.jpg
107 ms
logo_header.png
106 ms
GNMap212X115.jpg
103 ms
road_maint_map_promo.png
102 ms
opendatapreview.JPG
104 ms
newimproved.png
106 ms
ga.js
77 ms
transit.ashx
1801 ms
feature.ashx
69 ms
featurecollection.ashx
91 ms
featurecollection.ashx
103 ms
anonsecurity.ashx
383 ms
entersite.png
74 ms
residential.png
70 ms
addrrange.png
96 ms
dollarsign.png
133 ms
etsbus.png
139 ms
devapplications.png
143 ms
smily.png
148 ms
drivingdirections3.png
154 ms
busroutes.png
196 ms
landsales.png
208 ms
legaldescr.png
222 ms
municipal.png
225 ms
namedlocations.png
218 ms
neigh.png
258 ms
school2.png
276 ms
sports.png
276 ms
citygov.png
291 ms
__utm.gif
19 ms
__utm.gif
16 ms
feature.ashx
302 ms
maps.edmonton.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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
maps.edmonton.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
maps.edmonton.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maps.edmonton.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Maps.edmonton.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.
maps.edmonton.ca
Open Graph description is not detected on the main page of Maps Edmonton. 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: