3.6 sec in total
425 ms
2.6 sec
663 ms
Click here to check amazing Hollard content for South Africa. Otherwise, check out these important facts you probably never knew about hollard.co.za
Insure what you love through any of our brokers or partners
Visit hollard.co.zaWe analyzed Hollard.co.za page load time and found that the first response time was 425 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.
hollard.co.za performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value8.3 s
2/100
25%
Value7.1 s
31/100
10%
Value930 ms
30/100
30%
Value0.159
73/100
15%
Value10.8 s
22/100
10%
425 ms
967 ms
90 ms
184 ms
271 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 95% of them (53 requests) were addressed to the original Hollard.co.za, 4% (2 requests) were made to Platform.twitter.com and 2% (1 request) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Hollard.co.za.
Page size can be reduced by 179.9 kB (31%)
576.9 kB
396.9 kB
In fact, the total size of Hollard.co.za main page is 576.9 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. 45% of websites need less resources to load. Images take 371.3 kB which makes up the majority of the site volume.
Potential reduce by 179.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. 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 179.9 kB or 88% of the original size.
Potential reduce by 0 B
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. Hollard images are well optimized though.
Number of requests can be reduced by 23 (43%)
54
31
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hollard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
hollard.co.za
425 ms
www.hollard.co.za
967 ms
widgets.js
90 ms
fc3aa036400b5b28.css
184 ms
5022c6ca0ff4b9d0.css
271 ms
7aa30ece5f1b1dab.css
335 ms
polyfills-c67a75d1b6f99dc8.js
415 ms
webpack-2a7e4f992a9bc26b.js
375 ms
framework-2c79e2a64abdb08b.js
431 ms
main-7d4621788995fbc6.js
437 ms
_app-2a203fb4b1debdfd.js
376 ms
651-d23d2dd4bf7b98f3.js
503 ms
262-d77b1529538d425b.js
668 ms
210-bac0dcc540bc75f8.js
443 ms
%5B%5B...route%5D%5D-1dbcf53c3573037d.js
504 ms
_buildManifest.js
509 ms
_ssgManifest.js
518 ms
hollard-logo-white.8b55d018.svg
528 ms
search-temp.c8faef6b.svg
589 ms
hamburger-menu-white.f2f9831d.svg
591 ms
hollard_homepage_africa_header.svg
816 ms
hollard_contract-icon.svg
605 ms
hollard_corner-right-arrow_button_purple.860ff7cf.svg
614 ms
hollard_corner-right-arrow_button_orange.83110636.svg
677 ms
hollard_money-bay_icon.svg
680 ms
hollard_voucher-icon.svg
698 ms
next-arrow-purple.c3304ab3.svg
706 ms
image
783 ms
image
769 ms
image
797 ms
image
802 ms
image
810 ms
image
868 ms
image
872 ms
image
886 ms
hollard_homepage_wawya_mobile.png
1057 ms
arrow-right-white.36232772.svg
896 ms
hollard_homepage_life-and-stuff.svg
905 ms
hollard_homepage_business-and-people.svg
907 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
55 ms
settings
100 ms
hollard_homepage_invest-save.svg
778 ms
hollard_shopping_lady.svg
743 ms
hollard_walking-man.svg
647 ms
image
648 ms
image
712 ms
image
740 ms
hollard_footer.svg
654 ms
hollard_social_twitter_white.7af4b87b.svg
648 ms
hollard_social_facebook_white.57abb1b6.svg
657 ms
hollard_social_instagram_white.005e6248.svg
652 ms
hollard_social_linkedin_white.aa2cd4a8.svg
669 ms
hollard_social_youtube_white.9565e640.svg
667 ms
down-arrow-white.0922b9ae.svg
659 ms
south-africa-flag.28615b9a.svg
656 ms
down-arrow.7457df2b.svg
652 ms
hollard.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.
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
Document doesn't have a <title> element
hollard.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
Browser errors were logged to the console
hollard.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
Document doesn't have a <title> element
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hollard.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 Hollard.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.
hollard.co.za
Open Graph data is detected on the main page of Hollard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: