3.2 sec in total
1.1 sec
1.9 sec
196 ms
Welcome to mobile.knet.ca homepage info - get ready to check MOBILE K Net best content for Canada right away, or after learning these important things about mobile.knet.ca
Visit mobile.knet.caWe analyzed Mobile.knet.ca page load time and found that the first response time was 1.1 sec 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.
mobile.knet.ca performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value6.4 s
10/100
25%
Value6.8 s
34/100
10%
Value100 ms
98/100
30%
Value0.001
100/100
15%
Value5.8 s
67/100
10%
1070 ms
86 ms
90 ms
92 ms
93 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that all of those requests were addressed to Mobile.knet.ca and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Mobile.knet.ca.
Page size can be reduced by 298.8 kB (42%)
711.7 kB
412.8 kB
In fact, the total size of Mobile.knet.ca main page is 711.7 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. 30% of websites need less resources to load. Images take 346.9 kB which makes up the majority of the site volume.
Potential reduce by 27.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. 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 27.9 kB or 82% of the original size.
Potential reduce by 17.8 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. MOBILE K Net images are well optimized though.
Potential reduce by 171.2 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 171.2 kB or 76% of the original size.
Potential reduce by 81.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. Mobile.knet.ca needs all CSS files to be minified and compressed as it can save up to 81.9 kB or 78% of the original size.
Number of requests can be reduced by 49 (78%)
63
14
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MOBILE K Net. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
mobile.knet.ca
1070 ms
system.base.css
86 ms
system.menus.css
90 ms
system.messages.css
92 ms
system.theme.css
93 ms
views_slideshow.css
99 ms
date.css
99 ms
datepicker.1.7.css
128 ms
date_repeat_field.css
133 ms
field.css
133 ms
node.css
135 ms
search.css
137 ms
user.css
137 ms
views.css
170 ms
ckeditor.css
174 ms
ctools.css
174 ms
taxonomy_access.css
176 ms
views_slideshow_cycle.css
178 ms
superfish.css
179 ms
at.base.css
213 ms
at.layout.css
217 ms
at.messages.css
218 ms
html-elements.css
221 ms
forms.css
222 ms
tables.css
224 ms
page.css
257 ms
articles.css
261 ms
comments.css
262 ms
fields.css
264 ms
blocks.css
266 ms
navigation.css
268 ms
corolla.settings.style.css
302 ms
colors.css
304 ms
overrides.css
305 ms
print.css
308 ms
corolla.responsive.style.css
310 ms
corolla.responsive.gpanels.css
289 ms
corolla.responsive.layout.css
274 ms
jquery.min.js
372 ms
jquery.once.js
284 ms
drupal.js
279 ms
views_slideshow.js
279 ms
json2.js
280 ms
views_slideshow_cycle.js
276 ms
jquery.cycle.all.min.js
347 ms
jquery.hoverIntent.minified.js
288 ms
sftouchscreen.js
287 ms
supposition.js
286 ms
jquery.bgiframe.min.js
311 ms
superfish.js
309 ms
supersubs.js
306 ms
superfish.js
307 ms
logo.png
46 ms
mainBG.png
47 ms
Unnecto-RUSH-v4.png
175 ms
Unnecto-Quatto-X-v2.png
138 ms
Unnecto-Primo-3G-v4.png
138 ms
Unnecto-Air45-v4.png
181 ms
Unnecto-Air5-v3.png
224 ms
Unnecto-Air55-v2.png
175 ms
nav-inactive.png
183 ms
coverage-block.png
270 ms
logo-footer.png
219 ms
nav-active.png
46 ms
mobile.knet.ca accessibility score
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
Links do not have a discernible name
mobile.knet.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
mobile.knet.ca SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.knet.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 Mobile.knet.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.
mobile.knet.ca
Open Graph description is not detected on the main page of MOBILE K Net. 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: