6.7 sec in total
1.4 sec
5 sec
268 ms
Welcome to whoswho.co.za homepage info - get ready to check Whoswho best content for Pakistan right away, or after learning these important things about whoswho.co.za
Who? SA
Visit whoswho.co.zaWe analyzed Whoswho.co.za page load time and found that the first response time was 1.4 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
whoswho.co.za performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value2.8 s
84/100
25%
Value4.5 s
73/100
10%
Value1,240 ms
19/100
30%
Value0
100/100
15%
Value7.0 s
53/100
10%
1398 ms
2850 ms
2025 ms
1575 ms
447 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 25% of them (13 requests) were addressed to the original Whoswho.co.za, 45% (24 requests) were made to Whoswhosa.co.za.s3.amazonaws.com and 8% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Whoswho.co.za.
Page size can be reduced by 253.8 kB (25%)
999.7 kB
745.9 kB
In fact, the total size of Whoswho.co.za main page is 999.7 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. 50% of websites need less resources to load. Images take 666.7 kB which makes up the majority of the site volume.
Potential reduce by 28.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 28.4 kB or 75% of the original size.
Potential reduce by 18.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. Whoswho images are well optimized though.
Potential reduce by 77.7 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 77.7 kB or 57% of the original size.
Potential reduce by 128.9 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. Whoswho.co.za needs all CSS files to be minified and compressed as it can save up to 128.9 kB or 81% of the original size.
Number of requests can be reduced by 18 (35%)
51
33
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whoswho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
whoswho.co.za
1398 ms
css_50a9e31f2a6c823df2ac58e14dea9809.css
2850 ms
jquery-1.6.2.min.js
2025 ms
js_2c4e6ae3f8aab32e32944743b2666c26.js
1575 ms
value_proposition.js
447 ms
wwsa-jquery.js
446 ms
bg.png
131 ms
prum.min.js
10 ms
bg-home.png
114 ms
em.js
166 ms
menu-leaf.png
223 ms
logo.png
36 ms
bt-search.png
141 ms
bg-props.jpg
68 ms
props.png
68 ms
prop-be-seen.png
69 ms
prop-grow.png
150 ms
prop-connect.png
78 ms
prop-showcase.png
104 ms
login.png
100 ms
sprite.png
102 ms
sash-new.png
136 ms
lightShadeCorner.png
157 ms
whiteBG_opacity25.png
138 ms
picture-1871747.jpg
228 ms
picture-1871536.jpg
160 ms
picture-1866656.jpg
164 ms
picture-5234.jpg
165 ms
picture-7870.jpg
180 ms
picture-3562.jpg
269 ms
picture-69950.jpg
177 ms
picture-927.jpg
226 ms
picture-1113.jpg
226 ms
picture-897.jpg
440 ms
picture-2169.jpg
658 ms
Jody%20Paulsen_sml.jpg
652 ms
sdk.js
166 ms
sprite-statuses.png
217 ms
intersrc-webfont.woff
684 ms
widgets.js
13 ms
social.png
155 ms
ga.js
25 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
31 ms
__utm.gif
37 ms
syndication
80 ms
634696352048488448
146 ms
45 ms
xd_arbiter.php
128 ms
xd_arbiter.php
260 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
LVPveP61_normal.png
116 ms
jot
24 ms
whoswho.co.za accessibility score
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
whoswho.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
whoswho.co.za SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoswho.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 Whoswho.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.
whoswho.co.za
Open Graph description is not detected on the main page of Whoswho. 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: