Tools & Wizards About Us
hollard.co.zm screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

hollard.co.zm

Insurance Provider | Car, Home, Life Insurance | Hollard Zambia

Page Load Speed

3.9 sec in total

First Response

526 ms

Resources Loaded

3 sec

Page Rendered

373 ms

hollard.co.zm screenshot

About Website

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.zm

Key Findings

We analyzed Hollard.co.zm page load time and found that the first response time was 526 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

hollard.co.zm performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value2,030 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value1.479

0/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

hollard.co.zm

526 ms

www.hollard.co.zm

636 ms

gtm.js

70 ms

font-awesome.min.css

94 ms

nice-select.min.css

240 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 70% of them (67 requests) were addressed to the original Hollard.co.zm, 5% (5 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (779 ms) belongs to the original domain Hollard.co.zm.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.7 kB (26%)

Content Size

321.5 kB

After Optimization

238.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Hollard.co.zm main page is 321.5 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. 70% of websites need less resources to load. Javascripts take 220.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 80.8 kB

  • Original 93.6 kB
  • After minification 82.7 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 10.9 kB, which is 12% 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 80.8 kB or 86% of the original size.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

  • Original 220.7 kB
  • After minification 220.7 kB
  • After compression 219.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 342 B

  • Original 7.2 kB
  • After minification 7.2 kB
  • After compression 6.8 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. Hollard.co.zm has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (75%)

Requests Now

85

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 85 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 42 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hollard.co.zm

hollard.co.zm

526 ms

www.hollard.co.zm

www.hollard.co.zm

636 ms

gtm.js

gtm.js

70 ms

font-awesome.min.css

font-awesome.min.css

94 ms

nice-select.min.css

nice-select.min.css

240 ms

flag-icon.min.css

flag-icon.min.css

279 ms

flatpickr.min.css

flatpickr.min.css

345 ms

flatpickr-override.min.css

flatpickr-override.min.css

343 ms

lity.min.css

lity.min.css

347 ms

jBox.min.css

jBox.min.css

351 ms

site.min.css

site.min.css

356 ms

modernizr-2.8.3-respond-1.4.2.min.js

modernizr-2.8.3-respond-1.4.2.min.js

431 ms

basic-document.min.css

basic-document.min.css

427 ms

button.min.css

button.min.css

455 ms

dropdown-link-selector.min.css

dropdown-link-selector.min.css

456 ms

simple-info-block.min.css

simple-info-block.min.css

456 ms

feature-info-block.min.css

feature-info-block.min.css

457 ms

overlay.min.css

overlay.min.css

513 ms

iframe-widget.min.css

iframe-widget.min.css

515 ms

accordion.min.css

accordion.min.css

516 ms

page-header.min.css

page-header.min.css

517 ms

sdk.js

sdk.js

22 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

608 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

566 ms

jquery.nice-select.min.js

jquery.nice-select.min.js

606 ms

jquery.nice-select-ie-fix.min.js

jquery.nice-select-ie-fix.min.js

606 ms

jquery.form-validator.min.js

jquery.form-validator.min.js

606 ms

jquery.serialize-object.min.js

jquery.serialize-object.min.js

605 ms

jquery.autocomplete.min.js

jquery.autocomplete.min.js

631 ms

iframeResizer.min.js

iframeResizer.min.js

697 ms

flatpickr.min.js

flatpickr.min.js

693 ms

lity.min.js

lity.min.js

693 ms

js.cookie-2.2.0.min.js

js.cookie-2.2.0.min.js

691 ms

jBox.min.js

jBox.min.js

693 ms

hld-common.min.js

hld-common.min.js

704 ms

hld-resize.min.js

hld-resize.min.js

777 ms

hld-table.min.js

hld-table.min.js

778 ms

hld-search.min.js

hld-search.min.js

779 ms

social-media.min.css

social-media.min.css

779 ms

js

js

49 ms

analytics.js

analytics.js

21 ms

hld-footer.min.js

hld-footer.min.js

681 ms

collect

collect

91 ms

collect

collect

50 ms

hld-menu.min.js

hld-menu.min.js

550 ms

hld-accordion.min.js

hld-accordion.min.js

608 ms

ga-audiences

ga-audiences

28 ms

css

css

28 ms

cmb

cmb

500 ms

hollard-logo-1.svg

hollard-logo-1.svg

434 ms

search.svg

search.svg

435 ms

cancel.svg

cancel.svg

436 ms

sdk.js

sdk.js

4 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff

19 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo3cOWxw.woff

26 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo3cOWxw.woff

40 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdo3cOWxw.woff

65 ms

antartida-rounded-medium-webfont.woff

antartida-rounded-medium-webfont.woff

320 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

550 ms

antartida-rounded-bold-webfont.woff

antartida-rounded-bold-webfont.woff

391 ms

personal_header_final.jpg

personal_header_final.jpg

194 ms

hollard_zambia_travel-insurance_map.jpg

hollard_zambia_travel-insurance_map.jpg

391 ms

hollard_life-insurance_happy-family.jpg

hollard_life-insurance_happy-family.jpg

235 ms

hollard_car-insurance_happy-driver.jpg

hollard_car-insurance_happy-driver.jpg

254 ms

hollard_personal-accident_construction-worker.jpg

hollard_personal-accident_construction-worker.jpg

369 ms

hollard-zambia_header_desktop.jpg

hollard-zambia_header_desktop.jpg

376 ms

widget.js

widget.js

433 ms

gtm.js

gtm.js

58 ms

css

css

15 ms

jBox-329380237724c03d7887281099398c69.css

jBox-329380237724c03d7887281099398c69.css

304 ms

widget.min-97839fa2ba391e658de49a3e4edca171.css

widget.min-97839fa2ba391e658de49a3e4edca171.css

306 ms

landing-page-cmb.min-125db7d115af9154a8fb505a84c04a9d.css

landing-page-cmb.min-125db7d115af9154a8fb505a84c04a9d.css

305 ms

jquery-1.12.0.min-cbb11b58473b2d672f4ed53abbb67336.js

jquery-1.12.0.min-cbb11b58473b2d672f4ed53abbb67336.js

305 ms

jquery.placeholder.min-ee60835ea8faa661d4e1ce6c1a97b141.js

jquery.placeholder.min-ee60835ea8faa661d4e1ce6c1a97b141.js

400 ms

jquery.form-validator.min-bf9a56f01a9b239fb99b2f80018b11f6.js

jquery.form-validator.min-bf9a56f01a9b239fb99b2f80018b11f6.js

417 ms

jBox.min-97c4127c3c12989d9ee66523a4fb5779.js

jBox.min-97c4127c3c12989d9ee66523a4fb5779.js

387 ms

iframeResizer.contentWindow.min-e03fb3c975393abb286d6a5b41bd362b.js

iframeResizer.contentWindow.min-e03fb3c975393abb286d6a5b41bd362b.js

426 ms

utils.min-6d5de39e99f1d82d2cb088029ad643f0.js

utils.min-6d5de39e99f1d82d2cb088029ad643f0.js

386 ms

response-handler.min-ddd04c5891f41cfbc485409f52f28330.js

response-handler.min-ddd04c5891f41cfbc485409f52f28330.js

397 ms

widget.min-8320e1747a0f117833adac31ecace74c.js

widget.min-8320e1747a0f117833adac31ecace74c.js

471 ms

validation.min-03f824bff7077348b09cc7afc96b4011.js

validation.min-03f824bff7077348b09cc7afc96b4011.js

470 ms

eCommerceTracking.min-285bc93a1b561e4f5317d27c33fb6b4c.js

eCommerceTracking.min-285bc93a1b561e4f5317d27c33fb6b4c.js

487 ms

83 ms

js

js

46 ms

144 ms

insight.min.js

insight.min.js

167 ms

linkid.js

linkid.js

11 ms

collect

collect

117 ms

collect

collect

35 ms

18 ms

css

css

15 ms

insight_tag_errors.gif

insight_tag_errors.gif

152 ms

hollard-spinner-0f2823342d420f6b2ec2a7162fe3b233.svg

hollard-spinner-0f2823342d420f6b2ec2a7162fe3b233.svg

171 ms

fbevents.js

fbevents.js

5 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff

6 ms

c6f14f7a-0691-4e94-b201-465dce84ef50

c6f14f7a-0691-4e94-b201-465dce84ef50

184 ms

Accessibility Review

hollard.co.zm accessibility score

76

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

hollard.co.zm best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

hollard.co.zm SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: