4.1 sec in total
684 ms
2.9 sec
533 ms
Click here to check amazing Mobileaxs content for Canada. Otherwise, check out these important facts you probably never knew about mobileaxs.ca
Visit mobileaxs.caWe analyzed Mobileaxs.ca page load time and found that the first response time was 684 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
mobileaxs.ca performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value4.3 s
42/100
25%
Value4.1 s
79/100
10%
Value30 ms
100/100
30%
Value0.158
73/100
15%
Value3.0 s
96/100
10%
684 ms
108 ms
117 ms
25 ms
75 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 88% of them (50 requests) were addressed to the original Mobileaxs.ca, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (962 ms) belongs to the original domain Mobileaxs.ca.
Page size can be reduced by 681.5 kB (35%)
2.0 MB
1.3 MB
In fact, the total size of Mobileaxs.ca main page is 2.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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 39.7 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 39.7 kB or 77% of the original size.
Potential reduce by 3.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. Mobileaxs images are well optimized though.
Potential reduce by 325.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 325.6 kB or 68% of the original size.
Potential reduce by 313.0 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. Mobileaxs.ca needs all CSS files to be minified and compressed as it can save up to 313.0 kB or 85% of the original size.
Number of requests can be reduced by 39 (78%)
50
11
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobileaxs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.mobileaxs.ca
684 ms
wp-emoji-release.min.js
108 ms
layerslider.css
117 ms
css
25 ms
styles.css
75 ms
bootstrap.css
216 ms
style.css
182 ms
scripts.css
114 ms
font-awesome.min.css
144 ms
responsive.css
189 ms
woocommerce.css
139 ms
css
19 ms
ajaxpaging.css
172 ms
jquery.js
277 ms
jquery-migrate.min.js
206 ms
layerslider.kreaturamedia.jquery.js
238 ms
greensock.js
237 ms
layerslider.transitions.js
239 ms
random-number.js
237 ms
waypoints.min.js
236 ms
waypoints-sticky.min.js
343 ms
jquery.infinite-carousel.js
275 ms
jquery.ajaxpaging.js.php
670 ms
js_composer_front.css
248 ms
comment-reply.min.js
248 ms
jquery.form.min.js
250 ms
scripts.js
248 ms
jquery.flexslider-min.js
249 ms
bootstrap.min.js
259 ms
jquery.infinitescroll.min.js
250 ms
jquery.manual-trigger.js
254 ms
jquery.isotope.min.js
265 ms
jquery.ba-bbq.min.js
263 ms
jquery.fancybox.js
320 ms
easing.js
319 ms
jquery.ui.totop.js
318 ms
post-like.min.js
320 ms
jquery.parallax-1.1.3.js
321 ms
jquery.scrollTo-1.4.2-min.js
331 ms
jquery.tweet.js
333 ms
wp-embed.min.js
336 ms
js_composer_front.js
325 ms
mobileaxs_authoizedTELUS-logo-450pxX100px.png
91 ms
navigation_divider.png
92 ms
blank.gif
90 ms
mobileaxs-logo.png
89 ms
www.mobileaxs.ca
962 ms
girl-slider-bkgrndimg2.jpg
954 ms
girl-callcenter-slider-bkgrndimg.jpg
956 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
66 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
67 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
67 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
66 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
66 ms
fontawesome-webfont.woff
129 ms
skin.css
654 ms
backtotop.png
43 ms
mobileaxs.ca accessibility score
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
Links do not have a discernible name
mobileaxs.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
mobileaxs.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobileaxs.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 Mobileaxs.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.
mobileaxs.ca
Open Graph description is not detected on the main page of Mobileaxs. 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: