2.7 sec in total
140 ms
2.4 sec
157 ms
Visit enterprise.ca now to see the best up-to-date Enterprise content for Canada and also check out these interesting facts you probably never knew about enterprise.ca
Enjoy easy booking with thousands of airport and city locations near you. Lock in great rates when you book a rental car with Enterprise.
Visit enterprise.caWe analyzed Enterprise.ca page load time and found that the first response time was 140 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
enterprise.ca performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value10.2 s
0/100
25%
Value10.6 s
7/100
10%
Value7,950 ms
0/100
30%
Value0.037
100/100
15%
Value27.5 s
0/100
10%
140 ms
14 ms
18 ms
84 ms
105 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 26% of them (29 requests) were addressed to the original Enterprise.ca, 15% (17 requests) were made to Assets.adobedtm.com and 5% (6 requests) were made to Dsum-sec.casalemedia.com. The less responsive or slowest element that took the longest time to load (467 ms) relates to the external source Pc1.yumenetworks.com.
Page size can be reduced by 4.5 MB (34%)
13.0 MB
8.6 MB
In fact, the total size of Enterprise.ca main page is 13.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.0 MB which makes up the majority of the site volume.
Potential reduce by 184.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 184.6 kB or 81% of the original size.
Potential reduce by 37.4 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. Enterprise images are well optimized though.
Potential reduce by 1.4 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.4 MB or 74% of the original size.
Potential reduce by 2.8 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. Enterprise.ca needs all CSS files to be minified and compressed as it can save up to 2.8 MB or 72% of the original size.
Number of requests can be reduced by 63 (68%)
93
30
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enterprise. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
enterprise.ca
140 ms
home.html
14 ms
main-init.min.css
18 ms
conversion_async.js
84 ms
satelliteLib-64715503a5c3f03a9c38350e5a8825412fb1d39a.js
105 ms
common.min.js
40 ms
prod-libs.min.js
40 ms
en.i18nmap.js
36 ms
home.min.js
36 ms
content.min.js
37 ms
print.css
5 ms
mbox-contents-acd0be0245ac9c3b7e8a94d4d4491c612f0bcb5f.js
18 ms
satellite-5612c9ad6264300017000498.js
40 ms
satellite-561bd64f343930001700028a.js
58 ms
satellite-5616d3026266640017000d2a.js
221 ms
satellite-58f883d764746d2d7b007993.js
57 ms
satellite-55ca5ab438373100170007d4.js
55 ms
satellite-5980b7f964746d54d6009d2d.js
54 ms
satellite-560daa7962306507ba0009c3.js
54 ms
logo-enterprise.png
159 ms
nav-rent-weekend-special.jpg
133 ms
nav-share.jpg
138 ms
nav-learn.jpg
134 ms
nav-inspiration-ca.jpg
136 ms
nav-locations.jpg
134 ms
en_ca.svg
132 ms
en_ca.png
134 ms
ad-choices-icon-transparent.png
135 ms
browser-language
427 ms
63 ms
satellite-5988655b64746d57260007ec.js
51 ms
analytics.js
57 ms
s-code-contents-d6260cd16c768a70ed750852d8a333b8ed6e5e45.js
42 ms
satellite-56c637f264746d3a960005fc.js
37 ms
satellite-568a9b3164746d2e12009df8.js
57 ms
satellite-56b8c24764746d38c700037d.js
53 ms
drive-acadia-big-lighthouse.jpg
32 ms
inspiration-banff-ca.jpg
33 ms
rd
104 ms
conv
219 ms
46 ms
collect
48 ms
addthis_widget.js
102 ms
8f47fad3-ad6e-4b42-8277-01bbb0c45f4f.js
249 ms
main.min.css
26 ms
webfonts.min.css
47 ms
dest5.html
255 ms
id
223 ms
icons.min.css
126 ms
_ate.track.config_resp
197 ms
300lo.json
190 ms
20007504-6ea2-4d68-93e4-f4769b5d9f14.woff
68 ms
07d62b21-8d7a-4c36-be86-d32ab1089972.woff
81 ms
109143ca-57fb-459c-9814-3a68f0245ac3.woff
67 ms
e8e32219-8ee9-4d4b-ad86-de14076364f2.woff
67 ms
97b0cc11-9afb-4a2f-93b7-e1b5c40d80a6.woff
67 ms
sh.48536d49e4da3bdba54606b4.html
73 ms
clear-reservation
135 ms
static.css
63 ms
8f47fad3-ad6e-4b42-8277-01bbb0c45f4f.js
77 ms
WR-latest.js
88 ms
json
319 ms
s98031526387203
52 ms
current-session
175 ms
ibs:dpid=411&dpuuid=Wa8vlwAAAFHKe2dN
173 ms
layers.0ee9c4d64cf5ebc35dab.js
11 ms
ChangeMonitor-latest.js
172 ms
satellite-5612dc4b3766396c200008a0.html
20 ms
json
7 ms
activityi;src=3812164;type=enpr2013;cat=enter394;ord=2559794569388.0317
111 ms
fbevents.js
71 ms
activityi;src=959881;type=enter816;cat=homep765;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1569383025635.034
102 ms
lb
149 ms
47 ms
hbjs
279 ms
o.js
49 ms
49 ms
beacon_call.js
191 ms
1201292983320707
45 ms
tr
29 ms
adServerESI.aspx
111 ms
pix.js
65 ms
hbpix
125 ms
dynamic_rmpixel_2727.gif
467 ms
pixel
72 ms
pixel
74 ms
26 ms
37 ms
appnexus
47 ms
pix.js
20 ms
lb
26 ms
17 ms
usersync
84 ms
1
89 ms
rtset
52 ms
rum
98 ms
19 ms
21 ms
beacon
26 ms
rum
78 ms
rum
65 ms
22 ms
pixel
15 ms
rum
23 ms
rum
16 ms
rum
11 ms
pixel.gif
190 ms
rightmedia
13 ms
4 ms
tap.php
8 ms
rubicon
4 ms
satellite-5968c1af64746d020300a808.js
27 ms
satellite-58c314ab64746d4320003687.js
14 ms
enterprise.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 have valid values
ARIA IDs are not unique
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
Heading elements are not in a sequentially-descending order
enterprise.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
enterprise.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enterprise.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 Enterprise.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.
enterprise.ca
Open Graph description is not detected on the main page of Enterprise. 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: