3.5 sec in total
304 ms
2.7 sec
458 ms
Click here to check amazing Phonefinder content for South Africa. Otherwise, check out these important facts you probably never knew about phonefinder.co.za
Browse more than 1000 cellphone contract deals for any mobile device across all mobile networks at Phonefinder.co.za
Visit phonefinder.co.zaWe analyzed Phonefinder.co.za page load time and found that the first response time was 304 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
phonefinder.co.za performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value23.7 s
0/100
25%
Value16.8 s
0/100
10%
Value10,280 ms
0/100
30%
Value1
2/100
15%
Value24.3 s
0/100
10%
304 ms
1358 ms
25 ms
416 ms
181 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 68% of them (50 requests) were addressed to the original Phonefinder.co.za, 11% (8 requests) were made to Tpc.googlesyndication.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Phonefinder.co.za.
Page size can be reduced by 530.1 kB (40%)
1.3 MB
786.1 kB
In fact, the total size of Phonefinder.co.za main page is 1.3 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. 55% of websites need less resources to load. Images take 606.3 kB which makes up the majority of the site volume.
Potential reduce by 72.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. This page needs HTML code to be minified as it can gain 32.1 kB, which is 39% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 72.9 kB or 89% of the original size.
Potential reduce by 23.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. Phonefinder images are well optimized though.
Potential reduce by 394.5 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 394.5 kB or 68% of the original size.
Potential reduce by 39.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. Phonefinder.co.za needs all CSS files to be minified and compressed as it can save up to 39.6 kB or 80% of the original size.
Number of requests can be reduced by 29 (43%)
67
38
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
phonefinder.co.za
304 ms
www.phonefinder.co.za
1358 ms
css
25 ms
styles.min.css
416 ms
main-menu.min.css
181 ms
jquery.selectBox.min.css
257 ms
colorbox.min.css
265 ms
modal.min.css
163 ms
tracking.min.js
249 ms
head.load.min.js
90 ms
jquery-1.9.1.min.js
475 ms
modal.min.js
83 ms
analytics.js
60 ms
hotjar-55651.js
112 ms
gpt.js
58 ms
newsletter-left.gif
185 ms
reminder-left.gif
96 ms
social.jpg
188 ms
st-1-back.gif
185 ms
s-tick.png
185 ms
logo-main.png
205 ms
jquery.selectBox-arrow.gif
205 ms
top-left-new.gif
271 ms
phill-new.png
349 ms
top-left-button-new.png
223 ms
62-0.jpg
282 ms
63-0.jpg
290 ms
64-0.jpg
298 ms
65-0.jpg
496 ms
66-0.jpg
469 ms
67-0.jpg
469 ms
huawei_ascend_p8.jpg
473 ms
mtn.jpg
484 ms
telkom.jpg
493 ms
samsung_galaxy_tab_3.jpg
492 ms
cellc.jpg
494 ms
blackberry_leap.jpg
538 ms
apple_iphone_5s.jpg
539 ms
samsung_galaxy_a5.jpg
580 ms
samsung_galaxy_s6_flat.jpg
592 ms
samsung_galaxy_j1.jpg
583 ms
vodacom.jpg
589 ms
huawei-y6.jpg
684 ms
result-comp-but-arrow.png
585 ms
info.png
631 ms
button-arrow.png
645 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
51 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
52 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
144 ms
pubads_impl_81.js
22 ms
collect
97 ms
modules-41154dcc2471ae5ffaca14bb84e00edb.js
120 ms
ads
217 ms
container.html
31 ms
collect
72 ms
sfooter-arrow.gif
465 ms
ga-audiences
40 ms
jquery.selectBox.min.js
333 ms
jquery.cycle.all.min.js
350 ms
app-jq-home.min.js
385 ms
app-jq-top-search.min.js
399 ms
jquery.colorbox-min.js
427 ms
jquery.dropdownPlain.min.js
427 ms
bat.js
102 ms
imgad
100 ms
imgad
53 ms
imgad
64 ms
imgad
69 ms
imgad
66 ms
imgad
60 ms
imgad
56 ms
osd.js
29 ms
visit-data
231 ms
top-menu-over.gif
94 ms
phonefinder.co.za accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
phonefinder.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
phonefinder.co.za SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phonefinder.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 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.
phonefinder.co.za
Open Graph description is not detected on the main page of 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: