10.5 sec in total
994 ms
9.3 sec
243 ms
Click here to check amazing Pkf content for South Africa. Otherwise, check out these important facts you probably never knew about pkf.co.za
Visit pkf.co.zaWe analyzed Pkf.co.za page load time and found that the first response time was 994 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pkf.co.za performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value10.1 s
0/100
25%
Value2.9 s
94/100
10%
Value730 ms
40/100
30%
Value0.009
100/100
15%
Value8.8 s
36/100
10%
994 ms
879 ms
1085 ms
1762 ms
1633 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 64% of them (65 requests) were addressed to the original Pkf.co.za, 22% (22 requests) were made to Maps.googleapis.com and 7% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Pkf.co.za.
Page size can be reduced by 723.0 kB (51%)
1.4 MB
707.0 kB
In fact, the total size of Pkf.co.za main page is 1.4 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. 60% of websites need less resources to load. Javascripts take 729.6 kB which makes up the majority of the site volume.
Potential reduce by 65.5 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 65.5 kB or 85% of the original size.
Potential reduce by 14.4 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. Pkf images are well optimized though.
Potential reduce by 501.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 501.6 kB or 69% of the original size.
Potential reduce by 141.5 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. Pkf.co.za needs all CSS files to be minified and compressed as it can save up to 141.5 kB or 81% of the original size.
Number of requests can be reduced by 60 (65%)
92
32
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pkf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
pkf.co.za
994 ms
pkf.css
879 ms
rte.css
1085 ms
lightbox.css
1762 ms
jquery.js
1633 ms
jquery.resizeandcrop.js
1065 ms
pkf.js
1040 ms
lightbox.min.js
1556 ms
international.dev.css
2057 ms
responsive.css
1901 ms
responsive-footer.css
2056 ms
jsapi
23 ms
WebResource.axd
2131 ms
WebResource.axd
1799 ms
jquery.min.js
31 ms
scripts.js
2008 ms
pkf.map.js
2495 ms
jquery.prettyPhoto.js
2023 ms
contactForm.css
318 ms
header.css
626 ms
findAMemberControl.css
516 ms
navigation.css
627 ms
footer.css
515 ms
components.css
955 ms
whyChoosePkf.css
1914 ms
callToAction.css
1913 ms
MemberSpotlight.css
1670 ms
imageComponent.css
2207 ms
news.css
1922 ms
publications.css
2208 ms
listControl.css
2386 ms
officeMap.css
2829 ms
twitter.css
3177 ms
LinkedIn.css
2912 ms
paging.css
3219 ms
search.css
3031 ms
carousel.css
3219 ms
prettyPhoto.css
3421 ms
lightboxVideoList.css
3460 ms
OfficeAtoZ.css
3461 ms
international.only.css
3608 ms
people.css
3549 ms
handheld.css
3609 ms
south_africa_background.jpg
1179 ms
close.png
650 ms
loading.gif
526 ms
prev.png
504 ms
next.png
524 ms
pkf=logo.png
813 ms
PEstadium_carousel_img.jpg
1427 ms
Capetownstadium_carousel_img.jpg
1180 ms
Durbanstadium_carousel_img.jpg
1511 ms
ImageGen.ashx
961 ms
ImageGen.ashx
965 ms
ImageGen.ashx
1372 ms
ImageGen.ashx
1053 ms
ImageGen.ashx
1600 ms
twitter_30x30.png
1517 ms
linkedin_30x30.png
1437 ms
facebook_30x30.png
1971 ms
js
41 ms
opensans-regular-webfont.woff
1544 ms
pkf.woff
1566 ms
opensans-light-webfont.woff
1776 ms
opensans-semibold-webfont.woff
1793 ms
print.min.css
165 ms
common.js
19 ms
map.js
40 ms
util.js
71 ms
marker.js
36 ms
overlay.js
34 ms
StaticMapService.GetMapImage
99 ms
onion.js
22 ms
openhand_8_8.cur
47 ms
ViewportInfoService.GetViewportInfo
85 ms
stats.js
32 ms
controls.js
28 ms
infowindow.js
52 ms
pkf_number_small.png
391 ms
transparent.png
35 ms
css
88 ms
google4.png
68 ms
pkf_single.png
284 ms
mapcnt6.png
50 ms
vt
39 ms
vt
32 ms
vt
33 ms
vt
51 ms
vt
34 ms
vt
20 ms
vt
33 ms
vt
51 ms
vt
50 ms
tmapctrl.png
18 ms
cb_scout5.png
30 ms
tmapctrl4.png
19 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
13 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
27 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
27 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
27 ms
AuthenticationService.Authenticate
64 ms
pkf.co.za accessibility score
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
Buttons do not have an accessible name
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
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pkf.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pkf.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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pkf.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 Pkf.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.
pkf.co.za
Open Graph description is not detected on the main page of Pkf. 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: