Tools & Wizards About Us
mobilecompare.co.nz screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

mobilecompare.co.nz

Compare Mobile Phones & Providers

Page Load Speed

3.1 sec in total

First Response

285 ms

Resources Loaded

2.5 sec

Page Rendered

323 ms

mobilecompare.co.nz screenshot

About Website

Welcome to mobilecompare.co.nz homepage info - get ready to check Mobile Compare best content right away, or after learning these important things about mobilecompare.co.nz

Mobile Compare | Compare Mobile Plans and Compare Mobile Networks and Phones. Compare now.

Visit mobilecompare.co.nz

Key Findings

We analyzed Mobilecompare.co.nz page load time and found that the first response time was 285 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

mobilecompare.co.nz performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value1,540 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

mobilecompare.co.nz

285 ms

mobilecompare.co.nz

390 ms

www.mobilecompare.co.nz

482 ms

frontend-45bc6cb54061278a06b59e35b9bb06e9.css

63 ms

gpt.js

105 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Mobilecompare.co.nz, 53% (29 requests) were made to D18wxb31luze0u.cloudfront.net and 18% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (751 ms) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.9 kB (17%)

Content Size

852.2 kB

After Optimization

705.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobilecompare.co.nz main page is 852.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 426.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 55.4 kB

  • Original 65.6 kB
  • After minification 59.6 kB
  • After compression 10.2 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 55.4 kB or 84% of the original size.

Image Optimization

-21%

Potential reduce by 91.5 kB

  • Original 426.3 kB
  • After minification 334.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. Obviously, Mobile Compare needs image optimization as it can save up to 91.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 24 B

  • Original 298.6 kB
  • After minification 298.6 kB
  • After compression 298.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

-0%

Potential reduce by 0 B

  • Original 61.7 kB
  • After minification 61.7 kB
  • After compression 61.7 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. Mobilecompare.co.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (15%)

Requests Now

39

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobilecompare.co.nz

mobilecompare.co.nz

285 ms

mobilecompare.co.nz

mobilecompare.co.nz

390 ms

www.mobilecompare.co.nz

www.mobilecompare.co.nz

482 ms

frontend-45bc6cb54061278a06b59e35b9bb06e9.css

frontend-45bc6cb54061278a06b59e35b9bb06e9.css

63 ms

gpt.js

gpt.js

105 ms

css

css

84 ms

all.css

all.css

225 ms

js

js

139 ms

frontend-7dc33a0de916227b8bf7db552e084c2d.js

frontend-7dc33a0de916227b8bf7db552e084c2d.js

82 ms

pubads_impl.js

pubads_impl.js

38 ms

js

js

85 ms

gtm.js

gtm.js

123 ms

tag.js

tag.js

153 ms

mobilec-background.png

mobilec-background.png

133 ms

logo.png

logo.png

133 ms

logo.png

logo.png

134 ms

004-infinity.png

004-infinity.png

132 ms

dual.png

dual.png

138 ms

007-piggy-bank.png

007-piggy-bank.png

138 ms

005-rocket.png

005-rocket.png

140 ms

008-money.png

008-money.png

141 ms

006-calendar.png

006-calendar.png

145 ms

samsung_galaxy_2024.jpg:news-medium

samsung_galaxy_2024.jpg:news-medium

144 ms

blue-logo_1.png

blue-logo_1.png

144 ms

download_1.png

download_1.png

144 ms

farmside_logo_resized_1.png

farmside_logo_resized_1.png

144 ms

fibercity-logo-140.png

fibercity-logo-140.png

146 ms

kogan_mobile-230_1.jpg

kogan_mobile-230_1.jpg

146 ms

MightyMobile-Logo-Black--1-.png

MightyMobile-Logo-Black--1-.png

146 ms

Nova-logo_Mobile-Compare_1.-230x230_1.png

Nova-logo_Mobile-Compare_1.-230x230_1.png

273 ms

rsz_1onenz_-_230x277_1.jpg

rsz_1onenz_-_230x277_1.jpg

146 ms

Orcon-horiz-140.png

Orcon-horiz-140.png

145 ms

primo-logo_Dark-text230x80px.png

primo-logo_Dark-text230x80px.png

223 ms

Rocket-Mobile_Mobile-Compare_1.png

Rocket-Mobile_Mobile-Compare_1.png

224 ms

M.jpg

M.jpg

224 ms

28_med_slingshot140x140.png

28_med_slingshot140x140.png

147 ms

30_med_spark140x140.png

30_med_spark140x140.png

223 ms

M1.png

M1.png

225 ms

logo-dark.png

logo-dark.png

214 ms

arrow.png

arrow.png

185 ms

link-arrow.png

link-arrow.png

185 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

175 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

199 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

219 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

219 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

219 ms

fa-brands-400.woff

fa-brands-400.woff

237 ms

fa-solid-900.woff

fa-solid-900.woff

207 ms

fa-regular-400.woff

fa-regular-400.woff

186 ms

S6u8w4BMUTPHjxsAXC-v.ttf

S6u8w4BMUTPHjxsAXC-v.ttf

167 ms

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

166 ms

S6u-w4BMUTPHjxsIPx-oPCc.ttf

S6u-w4BMUTPHjxsIPx-oPCc.ttf

152 ms

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

167 ms

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

167 ms

advert.gif

advert.gif

751 ms

Accessibility Review

mobilecompare.co.nz accessibility score

98

Accessibility Issues

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

Links do not have a discernible name

Best Practices

mobilecompare.co.nz best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mobilecompare.co.nz SEO score

83

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Mobilecompare.co.nz 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 Mobilecompare.co.nz 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

mobilecompare.co.nz

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