Tools & Wizards About Us
valuemobile.ca screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

valuemobile.ca

Best Prepaid Cell Phone Plans in Canada | Value Mobile

Page Load Speed

6 sec in total

First Response

1.3 sec

Resources Loaded

4.5 sec

Page Rendered

222 ms

valuemobile.ca screenshot

About Website

Welcome to valuemobile.ca homepage info - get ready to check Value Mobile best content right away, or after learning these important things about valuemobile.ca

Choose Best Prepaid Cell Phone Plans in Canada for your smartphone. Compare and find the cell phone plans with competitive prices and services.

Visit valuemobile.ca

Key Findings

We analyzed Valuemobile.ca page load time and found that the first response time was 1.3 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

valuemobile.ca performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value460 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

valuemobile.ca

1250 ms

extendify-utilities.css

72 ms

styles.css

71 ms

jquery-ui.css

76 ms

user-front.css

75 ms

Our browser made a total of 183 requests to load all elements on the main page. We found that 89% of them (163 requests) were addressed to the original Valuemobile.ca, 7% (12 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Valuemobile.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 294.6 kB (20%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Valuemobile.ca main page is 1.5 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. 70% of websites need less resources to load. Javascripts take 740.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 84.8 kB

  • Original 109.9 kB
  • After minification 106.3 kB
  • After compression 25.1 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 84.8 kB or 77% of the original size.

Image Optimization

-32%

Potential reduce by 134.0 kB

  • Original 417.1 kB
  • After minification 283.0 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, Value Mobile needs image optimization as it can save up to 134.0 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-8%

Potential reduce by 56.3 kB

  • Original 740.9 kB
  • After minification 740.9 kB
  • After compression 684.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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 19.4 kB

  • Original 222.0 kB
  • After minification 222.0 kB
  • After compression 202.6 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. Valuemobile.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 145 (86%)

Requests Now

169

After Optimization

24

  • Images
  • JavaScript
  • CSS

The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Value Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 92 to 1 for JavaScripts and from 55 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

valuemobile.ca

valuemobile.ca

1250 ms

extendify-utilities.css

extendify-utilities.css

72 ms

styles.css

styles.css

71 ms

jquery-ui.css

jquery-ui.css

76 ms

user-front.css

user-front.css

75 ms

daterangepicker.css

daterangepicker.css

74 ms

front.css

front.css

93 ms

chosen.min.css

chosen.min.css

137 ms

by_author.css

by_author.css

138 ms

by_instock.css

by_instock.css

139 ms

by_onsales.css

by_onsales.css

140 ms

front.css

front.css

140 ms

label.css

label.css

163 ms

select_radio_check.css

select_radio_check.css

208 ms

checkbox.css

checkbox.css

211 ms

radio.css

radio.css

212 ms

switcher.css

switcher.css

210 ms

color.css

color.css

213 ms

tooltip.css

tooltip.css

229 ms

front.css

front.css

273 ms

switcher.css

switcher.css

276 ms

woocommerce-layout.css

woocommerce-layout.css

277 ms

woocommerce.css

woocommerce.css

280 ms

styles.min.css

styles.min.css

278 ms

jquery.bxslider.css

jquery.bxslider.css

294 ms

woocommerce-category-banner-management-public.css

woocommerce-category-banner-management-public.css

341 ms

all.min.css

all.min.css

344 ms

owl.carousel.min.css

owl.carousel.min.css

342 ms

owl.theme.min.css

owl.theme.min.css

346 ms

g-style.css

g-style.css

348 ms

css

css

36 ms

bootstrap.css

bootstrap.css

387 ms

animate.css

animate.css

411 ms

plugin.css

plugin.css

415 ms

font-awesome.css

font-awesome.css

417 ms

style.css

style.css

420 ms

style.css

style.css

421 ms

js

js

72 ms

js

js

70 ms

jquery.mb.YTPlayer.min.css

jquery.mb.YTPlayer.min.css

435 ms

css

css

14 ms

style.css

style.css

416 ms

woocommerce.css

woocommerce.css

419 ms

light.css

light.css

418 ms

js_composer.min.css

js_composer.min.css

468 ms

smartslider.min.css

smartslider.min.css

418 ms

wc-blocks.css

wc-blocks.css

432 ms

sections.css

sections.css

436 ms

tooltipster.bundle.min.css

tooltipster.bundle.min.css

436 ms

tooltipster-sideTip-noir.min.css

tooltipster-sideTip-noir.min.css

436 ms

ion.rangeSlider.css

ion.rangeSlider.css

437 ms

animate.min.css

animate.min.css

462 ms

front-builder.css

front-builder.css

447 ms

jquery.tabSlideOut.css

jquery.tabSlideOut.css

413 ms

slideout.css

slideout.css

414 ms

husky.js

husky.js

413 ms

jquery.min.js

jquery.min.js

438 ms

jquery-migrate.min.js

jquery-migrate.min.js

455 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

445 ms

add-to-cart.min.js

add-to-cart.min.js

414 ms

js.cookie.min.js

js.cookie.min.js

413 ms

woocommerce.min.js

woocommerce.min.js

413 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

437 ms

woocommerce-category-banner-management-public.min.js

woocommerce-category-banner-management-public.min.js

453 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

446 ms

jquery.js

jquery.js

469 ms

owl.carousel.min.js

owl.carousel.min.js

413 ms

custom.js

custom.js

410 ms

maplace.js

maplace.js

436 ms

jquery.malihu.PageScroll2id.js

jquery.malihu.PageScroll2id.js

453 ms

n2.min.js

n2.min.js

416 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

437 ms

ss-simple.min.js

ss-simple.min.js

408 ms

w-arrow-image.min.js

w-arrow-image.min.js

428 ms

index.js

index.js

445 ms

index.js

index.js

453 ms

jquery-ui.min.js

jquery-ui.min.js

636 ms

css

css

14 ms

style.css

style.css

435 ms

daterangepicker.js

daterangepicker.js

431 ms

pickup-script.js

pickup-script.js

530 ms

sourcebuster.min.js

sourcebuster.min.js

600 ms

order-attribution.min.js

order-attribution.min.js

571 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

602 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

626 ms

wp-polyfill.min.js

wp-polyfill.min.js

647 ms

react.min.js

react.min.js

625 ms

hooks.min.js

hooks.min.js

625 ms

deprecated.min.js

deprecated.min.js

633 ms

dom.min.js

dom.min.js

663 ms

react-dom.min.js

react-dom.min.js

701 ms

escape-html.min.js

escape-html.min.js

669 ms

element.min.js

element.min.js

670 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

658 ms

i18n.min.js

i18n.min.js

638 ms

keycodes.min.js

keycodes.min.js

662 ms

priority-queue.min.js

priority-queue.min.js

671 ms

compose.min.js

compose.min.js

674 ms

private-apis.min.js

private-apis.min.js

681 ms

redux-routine.min.js

redux-routine.min.js

658 ms

data.min.js

data.min.js

655 ms

lodash.min.js

lodash.min.js

690 ms

wc-blocks-registry.js

wc-blocks-registry.js

672 ms

url.min.js

url.min.js

670 ms

api-fetch.min.js

api-fetch.min.js

656 ms

wc-settings.js

wc-settings.js

640 ms

data-controls.min.js

data-controls.min.js

653 ms

html-entities.min.js

html-entities.min.js

681 ms

notices.min.js

notices.min.js

668 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

645 ms

wc-blocks-data.js

wc-blocks-data.js

680 ms

dom-ready.min.js

dom-ready.min.js

638 ms

a11y.min.js

a11y.min.js

651 ms

primitives.min.js

primitives.min.js

636 ms

gtm.js

gtm.js

194 ms

warning.min.js

warning.min.js

539 ms

blocks-components.js

blocks-components.js

565 ms

166 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

128 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

143 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

156 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

164 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

179 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

195 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

196 ms

blocks-checkout.js

blocks-checkout.js

508 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

500 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

110 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

112 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf

113 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

133 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf

618 ms

bootstrap.min.js

bootstrap.min.js

459 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

453 ms

total1.js

total1.js

456 ms

classie.js

classie.js

455 ms

wow.min.js

wow.min.js

455 ms

designesia.js

designesia.js

431 ms

tooltipster.bundle.min.js

tooltipster.bundle.min.js

433 ms

57 ms

front.js

front.js

418 ms

radio.js

radio.js

430 ms

checkbox.js

checkbox.js

428 ms

select.js

select.js

419 ms

mselect.js

mselect.js

423 ms

by_author.js

by_author.js

404 ms

by_instock.js

by_instock.js

430 ms

by_onsales.js

by_onsales.js

436 ms

front.js

front.js

433 ms

label.js

label.js

424 ms

sections.js

sections.js

421 ms

select_radio_check.js

select_radio_check.js

409 ms

front.js

front.js

402 ms

chosen.jquery.js

chosen.jquery.js

434 ms

ion.rangeSlider.min.js

ion.rangeSlider.min.js

425 ms

js_composer_front.min.js

js_composer_front.min.js

421 ms

vc-waypoints.min.js

vc-waypoints.min.js

434 ms

select.js

select.js

415 ms

jquery.tabSlideOut.js

jquery.tabSlideOut.js

409 ms

slideout.js

slideout.js

433 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

497 ms

find-icon.png

find-icon.png

463 ms

value-mobile-logo.png

value-mobile-logo.png

447 ms

valuemobile-homepage-banner-1.jpg

valuemobile-homepage-banner-1.jpg

474 ms

valuemobile-homepage-banner-3.jpg

valuemobile-homepage-banner-3.jpg

481 ms

headphone-pic.jpg

headphone-pic.jpg

491 ms

apple.jpg

apple.jpg

442 ms

google.jpg

google.jpg

447 ms

motorola-150x65.jpg

motorola-150x65.jpg

463 ms

samsung-150x65.jpg

samsung-150x65.jpg

460 ms

tcl.jpg

tcl.jpg

466 ms

zte.jpg

zte.jpg

453 ms

graphic.png

graphic.png

500 ms

chatr-carrier.jpg

chatr-carrier.jpg

457 ms

fido-carrier.jpg

fido-carrier.jpg

468 ms

freedom-carrier.jpg

freedom-carrier.jpg

469 ms

canada-sim2.jpg

canada-sim2.jpg

515 ms

map-pic.jpg

map-pic.jpg

479 ms

footer-logo.png

footer-logo.png

469 ms

fb.png

fb.png

476 ms

twitter.png

twitter.png

474 ms

linked.png

linked.png

494 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

39 ms

Accessibility Review

valuemobile.ca accessibility score

78

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

valuemobile.ca best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

valuemobile.ca SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Valuemobile.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 Valuemobile.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.

Social Sharing Optimization

valuemobile.ca

Open Graph data is detected on the main page of Value Mobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: