Tools & Wizards About Us
m.phonefinder.co.za screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

m.phonefinder.co.za

SA's #1 cellphone contract deals & data specials marketplace | Phonefinder.co.za

Page Load Speed

2.1 sec in total

First Response

327 ms

Resources Loaded

1.7 sec

Page Rendered

82 ms

m.phonefinder.co.za screenshot

About Website

Visit m.phonefinder.co.za now to see the best up-to-date M Phonefinder content for South Africa and also check out these interesting facts you probably never knew about m.phonefinder.co.za

Browse more than 1000 cellphone contract deals for any mobile device across all mobile networks at Phonefinder.co.za

Visit m.phonefinder.co.za

Key Findings

We analyzed M.phonefinder.co.za page load time and found that the first response time was 327 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

m.phonefinder.co.za performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value32.4 s

0/100

25%

SI (Speed Index)

Value24.4 s

0/100

10%

TBT (Total Blocking Time)

Value17,850 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.507

16/100

15%

TTI (Time to Interactive)

Value38.1 s

0/100

10%

Network Requests Diagram

browser-compatibility

327 ms

668b3ba.css

15 ms

4382f61.css

28 ms

cd2c187.css

324 ms

844436f.css

45 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 77% of them (24 requests) were addressed to the original M.phonefinder.co.za, 10% (3 requests) were made to Securepubads.g.doubleclick.net and 6% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (374 ms) belongs to the original domain M.phonefinder.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 385.7 kB (45%)

Content Size

849.8 kB

After Optimization

464.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of M.phonefinder.co.za main page is 849.8 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. 65% of websites need less resources to load. Javascripts take 776.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 52.9 kB

  • Original 65.3 kB
  • After minification 65.3 kB
  • After compression 12.4 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 52.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 7.7 kB
  • After minification 7.7 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. M Phonefinder images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 332.8 kB

  • Original 776.7 kB
  • After minification 776.7 kB
  • After compression 443.9 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 332.8 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (77%)

Requests Now

30

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

browser-compatibility

browser-compatibility

327 ms

668b3ba.css

668b3ba.css

15 ms

4382f61.css

4382f61.css

28 ms

cd2c187.css

cd2c187.css

324 ms

844436f.css

844436f.css

45 ms

e3e0e59.css

e3e0e59.css

31 ms

2f861cc.css

2f861cc.css

32 ms

ee47d12.png

ee47d12.png

25 ms

e062478.png

e062478.png

321 ms

f9cf2c3.png

f9cf2c3.png

37 ms

email-decode.min.js

email-decode.min.js

34 ms

33afede.js

33afede.js

43 ms

0314c26.js

0314c26.js

374 ms

ecb5946.js

ecb5946.js

58 ms

e4d0606.js

e4d0606.js

60 ms

a8b1ffc.js

a8b1ffc.js

57 ms

ba11e66.js

ba11e66.js

72 ms

e1f3adc.js

e1f3adc.js

82 ms

ef08b9b.js

ef08b9b.js

119 ms

60f6c17.js

60f6c17.js

90 ms

rocket-loader.min.js

rocket-loader.min.js

88 ms

1a5c8aa.png

1a5c8aa.png

100 ms

gpt.js

gpt.js

52 ms

adsbygoogle.js

adsbygoogle.js

170 ms

js

js

95 ms

google-tag-manager.js

google-tag-manager.js

309 ms

pubads_impl.js

pubads_impl.js

29 ms

ppub_config

ppub_config

140 ms

show_ads_impl.js

show_ads_impl.js

367 ms

teads-fellow.js

teads-fellow.js

31 ms

teads.js

teads.js

323 ms

Accessibility Review

m.phonefinder.co.za accessibility score

79

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

m.phonefinder.co.za 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

Displays images with incorrect aspect ratio

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

m.phonefinder.co.za SEO score

90

Search Engine Optimization Advices

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 M.phonefinder.co.za 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 M.phonefinder.co.za 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

m.phonefinder.co.za

Open Graph description is not detected on the main page of M Phonefinder. 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: