4.9 sec in total
131 ms
4.6 sec
207 ms
Welcome to nationalcar.ca homepage info - get ready to check National Car best content for Canada right away, or after learning these important things about nationalcar.ca
Join Emerald Club and enjoy exclusive benefits including counter bypass, choose your own car and earn rewards towards free rental days (select locations).
Visit nationalcar.caWe analyzed Nationalcar.ca page load time and found that the first response time was 131 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nationalcar.ca performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value16.9 s
0/100
25%
Value10.1 s
9/100
10%
Value6,280 ms
0/100
30%
Value0.103
89/100
15%
Value27.6 s
0/100
10%
131 ms
1390 ms
16 ms
44 ms
6 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 53% of them (59 requests) were addressed to the original Nationalcar.ca, 13% (14 requests) were made to Assets.adobedtm.com and 4% (4 requests) were made to Match.adsrvr.org. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nationalcar.ca.
Page size can be reduced by 1.9 MB (69%)
2.7 MB
849.9 kB
In fact, the total size of Nationalcar.ca main page is 2.7 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. 55% of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 120.9 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 20.9 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 120.9 kB or 84% of the original size.
Potential reduce by 51.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. Obviously, National Car needs image optimization as it can save up to 51.2 kB or 15% 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.5 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.5 MB or 75% of the original size.
Potential reduce by 241.3 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. Nationalcar.ca needs all CSS files to be minified and compressed as it can save up to 241.3 kB or 83% of the original size.
Number of requests can be reduced by 70 (68%)
103
33
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of National Car. 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 4 to 1 for CSS and as a result speed up the page load time.
nationalcar.ca
131 ms
www.nationalcar.ca
1390 ms
home.html
16 ms
satelliteLib-64715503a5c3f03a9c38350e5a8825412fb1d39a.js
44 ms
init.min.js
6 ms
jqueryOld.min.js
25 ms
clientlibrarymanager.min.js
23 ms
yzk0vyc.js
199 ms
eluminate.js
268 ms
mbox-contents-acd0be0245ac9c3b7e8a94d4d4491c612f0bcb5f.js
21 ms
satellite-560daa7962306507ba0009c3.js
20 ms
init.min.js
31 ms
jquery.min.js
28 ms
utils.min.js
31 ms
granite.min.js
31 ms
jquery.min.js
29 ms
jquery-ui.min.js
44 ms
jquery.min.js
41 ms
knockoutjs.min.js
33 ms
cookies.min.js
44 ms
analytics.min.js
39 ms
viewModel.min.js
42 ms
source.min.js
45 ms
modal.min.js
45 ms
header.min.js
67 ms
global.min.js
47 ms
homepage.min.js
45 ms
default.min.css
44 ms
default.min.css
67 ms
default.min.css
73 ms
default.min.css
48 ms
rd
8 ms
id
115 ms
head.js
294 ms
90406766.js
122 ms
dispatcher-v3.js
85 ms
yahoo-min.js
18 ms
cp-v3.js
111 ms
json-min.js
18 ms
locale%3Den_US.json
545 ms
1398181080356.png
10 ms
1398181093330.png
9 ms
1398181083573.png
10 ms
1398181082517.png
8 ms
1398181081657.png
9 ms
1398181081350.png
10 ms
1398181081350.png
12 ms
1426537461383.jpg
38 ms
1398181081350.png
9 ms
1345822881910.png
10 ms
1411636671220.png
10 ms
1412194780433.jpg
11 ms
1420036975644.jpg
11 ms
1454520253878.png
11 ms
AdChoices-icon_16x16.png
19 ms
facebook.png
14 ms
twitter.png
13 ms
youtube.png
14 ms
new-g-plus-icon-20.png
17 ms
1345822880973.png
17 ms
shared.min.js
14 ms
underscore.min.js
20 ms
kernel.min.js
22 ms
jcr:content.doi.full.high.heroImage.png
14 ms
caret.png
40 ms
ajax-loader-gray.gif
10 ms
national_footer_logo.png
30 ms
satellite-56bb602064746d4d87001255.js
23 ms
satellite-55822a90353466001700076c.js
18 ms
satellite-55822a8f3534660017000705.js
21 ms
satellite-55dcc28661656300140011ae.js
440 ms
satellite-55822a8f35346600170006f2.js
439 ms
satellite-55822a8f3534660017000656.html
445 ms
satellite-55822a8f35346600170005fb.html
444 ms
satellite-55e710843662372d84001319.js
437 ms
satellite-55e77ec56136640014000265.js
438 ms
satellite-55e6564a653364001400060c.js
437 ms
s-code-contents-d6260cd16c768a70ed750852d8a333b8ed6e5e45.js
435 ms
home.sfx.json
127 ms
locale%3Den_US.json
1412 ms
login_icon_16X15.png
46 ms
globe_icon_16X16.png
46 ms
fd5670e7-a222-42cd-baa3-2c2948fba406.js
136 ms
di.js
335 ms
s56199445137754
21 ms
cm
387 ms
activityi;src=3814167;type=natio832;cat=homep751;ord=7490249953698.367
124 ms
activityi;src=3814167;type=natio832;cat=reser648;ord=9792029445525.258
88 ms
WRf4.js
3 ms
50 ms
52 ms
53 ms
25 ms
o.js
188 ms
hbjs
167 ms
generic
28 ms
o
86 ms
pixel
44 ms
generic
5 ms
6 ms
match
3 ms
rum
64 ms
pixel
22 ms
Pug
75 ms
cm
79 ms
relator
73 ms
mapuser
7 ms
sd
16 ms
rum
10 ms
generic
6 ms
tap.php
1093 ms
ui-bg_flat_75_ffffff_40x100.png
14 ms
nationalcar.ca accessibility score
nationalcar.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
Missing source maps for large first-party JavaScript
nationalcar.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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nationalcar.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 Nationalcar.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.
nationalcar.ca
Open Graph description is not detected on the main page of National Car. 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: