3.7 sec in total
501 ms
2.9 sec
272 ms
Visit hollard.co.zm now to see the best up-to-date Hollard content and also check out these interesting facts you probably never knew about hollard.co.zm
Hollard Zambia, part of the Hollard Group which began in SA, along with specialised insurance partners, provides innovative insurance solutions to our clients
Visit hollard.co.zmWe analyzed Hollard.co.zm page load time and found that the first response time was 501 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 60% of websites can load faster.
hollard.co.zm performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value13.7 s
0/100
25%
Value9.3 s
12/100
10%
Value1,670 ms
11/100
30%
Value0.106
88/100
15%
Value18.8 s
3/100
10%
501 ms
989 ms
68 ms
90 ms
191 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 70% of them (65 requests) were addressed to the original Hollard.co.zm, 12% (11 requests) were made to Static.xx.fbcdn.net and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (989 ms) belongs to the original domain Hollard.co.zm.
Page size can be reduced by 88.6 kB (20%)
449.0 kB
360.4 kB
In fact, the total size of Hollard.co.zm main page is 449.0 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. 60% of websites need less resources to load. Javascripts take 271.9 kB which makes up the majority of the site volume.
Potential reduce by 87.8 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 87.8 kB or 86% of the original size.
Potential reduce by 21 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.
Potential reduce by 486 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 342 B
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. Hollard.co.zm has all CSS files already compressed.
Number of requests can be reduced by 65 (78%)
83
18
The browser has sent 83 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 43 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
hollard.co.zm
501 ms
www.hollard.co.zm
989 ms
gtm.js
68 ms
font-awesome.min.css
90 ms
nice-select.min.css
191 ms
flag-icon.min.css
280 ms
flatpickr.min.css
343 ms
flatpickr-override.min.css
342 ms
lity.min.css
346 ms
jBox.min.css
347 ms
site.min.css
354 ms
modernizr-2.8.3-respond-1.4.2.min.js
434 ms
basic-document.min.css
431 ms
button.min.css
474 ms
dropdown-link-selector.min.css
432 ms
simple-info-block.min.css
475 ms
feature-info-block.min.css
475 ms
overlay.min.css
518 ms
iframe-widget.min.css
518 ms
page-header.min.css
519 ms
sdk.js
41 ms
jquery-3.6.0.min.js
608 ms
jquery.mobile.custom.min.js
597 ms
jquery.nice-select.min.js
599 ms
jquery.nice-select-ie-fix.min.js
607 ms
jquery.form-validator.min.js
608 ms
jquery.serialize-object.min.js
606 ms
jquery.autocomplete.min.js
620 ms
iframeResizer.min.js
686 ms
flatpickr.min.js
700 ms
lity.min.js
698 ms
js.cookie-2.2.0.min.js
699 ms
jBox.min.js
699 ms
hld-common.min.js
706 ms
hld-resize.min.js
773 ms
hld-table.min.js
783 ms
hld-search.min.js
785 ms
hld-footer.min.js
786 ms
social-media.min.css
786 ms
hld-menu.min.js
711 ms
css
35 ms
cmb
461 ms
hollard-logo-1.svg
405 ms
search.svg
406 ms
cancel.svg
422 ms
hollard_homepage_header_cropped.svg
932 ms
sdk.js
22 ms
110 ms
ajax-loader.gif
367 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
28 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf
37 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
43 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf
43 ms
antartida-rounded-medium-webfont.woff
364 ms
antartida-rounded-bold-webfont.woff
364 ms
fontawesome-webfont.woff
560 ms
hollard_travel-insurance_product-card.jpg
196 ms
hollard_life-insurance_product-card.jpg
177 ms
hollard_car-insurance_product-card.jpg
198 ms
hollard_personal-accident-insurance_product-card.jpg
302 ms
page.php
92 ms
widget.js
28 ms
gtm.js
76 ms
css
20 ms
jBox-329380237724c03d7887281099398c69.css
236 ms
widget.min-97839fa2ba391e658de49a3e4edca171.css
267 ms
landing-page-cmb.min-125db7d115af9154a8fb505a84c04a9d.css
234 ms
jquery-1.12.0.min-cbb11b58473b2d672f4ed53abbb67336.js
302 ms
jquery.placeholder.min-ee60835ea8faa661d4e1ce6c1a97b141.js
299 ms
jquery.form-validator.min-bf9a56f01a9b239fb99b2f80018b11f6.js
329 ms
jBox.min-97c4127c3c12989d9ee66523a4fb5779.js
330 ms
iframeResizer.contentWindow.min-e03fb3c975393abb286d6a5b41bd362b.js
344 ms
utils.min-6d5de39e99f1d82d2cb088029ad643f0.js
390 ms
response-handler.min-ddd04c5891f41cfbc485409f52f28330.js
422 ms
widget.min-af5277c933284b9306dc63b587731f81.js
413 ms
validation.min-03f824bff7077348b09cc7afc96b4011.js
417 ms
eCommerceTracking.min-285bc93a1b561e4f5317d27c33fb6b4c.js
441 ms
eOzOzediAge.css
59 ms
MNN6HnO7RmE.js
86 ms
o1ndYS2og_B.js
84 ms
FsgTKAP125G.js
113 ms
pLoSlJD7y1F.js
113 ms
Glud--w-qOK.js
112 ms
WvbRbK9sYiL.js
84 ms
p55HfXW__mM.js
113 ms
ALTQi95mOyD.js
119 ms
447461119_848633807284111_362655519146304341_n.png
79 ms
347860158_1262897637954244_1547808247242569392_n.jpg
70 ms
X8OdVmaAGx4.js
26 ms
UXtr_j2Fwe-.png
24 ms
css
32 ms
hollard-spinner-0f2823342d420f6b2ec2a7162fe3b233.svg
262 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
8 ms
hollard.co.zm 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
hollard.co.zm 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
Page has valid source maps
hollard.co.zm SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Hollard.co.zm 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.zm 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.zm
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: