1.7 sec in total
302 ms
1.3 sec
105 ms
Click here to check amazing Nextlift content for Canada. Otherwise, check out these important facts you probably never knew about nextlift.ca
Visit nextlift.caWe analyzed Nextlift.ca page load time and found that the first response time was 302 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
nextlift.ca performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value7.3 s
4/100
25%
Value6.5 s
39/100
10%
Value430 ms
65/100
30%
Value0.625
10/100
15%
Value6.9 s
54/100
10%
302 ms
149 ms
436 ms
219 ms
325 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 53% of them (23 requests) were addressed to the original Nextlift.ca, 7% (3 requests) were made to Maxcdn.bootstrapcdn.com and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (485 ms) belongs to the original domain Nextlift.ca.
Page size can be reduced by 366.4 kB (60%)
607.4 kB
241.0 kB
In fact, the total size of Nextlift.ca main page is 607.4 kB. 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 250.3 kB which makes up the majority of the site volume.
Potential reduce by 11.8 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 22% 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 11.8 kB or 80% of the original size.
Potential reduce by 3.5 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. Nextlift images are well optimized though.
Potential reduce by 172.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 172.6 kB or 69% of the original size.
Potential reduce by 178.4 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. Nextlift.ca needs all CSS files to be minified and compressed as it can save up to 178.4 kB or 85% of the original size.
Number of requests can be reduced by 24 (63%)
38
14
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nextlift. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
nextlift.ca
302 ms
Leaflet.vector-markers.css
149 ms
bootstrap.css
436 ms
accordion.css
219 ms
tb-style.css
325 ms
tipsy.css
223 ms
leaflet.css
39 ms
font-awesome.min.css
10 ms
custom-modernizr.min.js
228 ms
knockout-3.1.0.js
84 ms
jquery.min.js
30 ms
leaflet.js
41 ms
bootstrap.min.js
27 ms
jquery-ui.js
24 ms
Leaflet.vector-markers.min.js
253 ms
bootstrap-toolkit.js
342 ms
jquery.autocomplete.min.js
345 ms
jquery.tipsy.js
344 ms
jquery.pathchange.js
372 ms
jquery.scrollintoview.min.js
423 ms
nextride.js
485 ms
logo_right_with_name.svg
485 ms
icon_wheelchair.png
485 ms
css
24 ms
left_bg_line.svg
134 ms
acircle.svg
127 ms
icon_gps.svg
128 ms
icon_search.svg
129 ms
bcircle.svg
130 ms
exclamcircle.svg
131 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
49 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
49 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
48 ms
fontawesome-webfont.woff
47 ms
353.png
383 ms
353.png
380 ms
354.png
350 ms
GetLines
227 ms
353.png
418 ms
353.png
359 ms
354.png
376 ms
354.png
404 ms
354.png
362 ms
nextlift.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
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.
nextlift.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
Page has valid source maps
nextlift.ca SEO score
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 doesn't use legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextlift.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Nextlift.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.
nextlift.ca
Open Graph description is not detected on the main page of Nextlift. 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: