Tools & Wizards About Us
marico.co.za screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

marico.co.za

Marico Tourism

Page Load Speed

4.1 sec in total

First Response

779 ms

Resources Loaded

2.5 sec

Page Rendered

780 ms

marico.co.za screenshot

About Website

Welcome to marico.co.za homepage info - get ready to check Marico best content for South Africa right away, or after learning these important things about marico.co.za

Tourism in the Marico District, North-West Province, South-Africa

Visit marico.co.za

Key Findings

We analyzed Marico.co.za page load time and found that the first response time was 779 ms and then it took 3.3 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

marico.co.za performance score

0

Network Requests Diagram

marico.co.za

779 ms

Marico1.htm

412 ms

Marico2.htm

547 ms

Image4.jpg

273 ms

380 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 16% of them (13 requests) were addressed to the original Marico.co.za, 20% (16 requests) were made to Google.com and 16% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (789 ms) belongs to the original domain Marico.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 535.0 kB (50%)

Content Size

1.1 MB

After Optimization

536.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Marico.co.za main page is 1.1 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. 55% of websites need less resources to load. Javascripts take 782.6 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 851 B

  • Original 1.7 kB
  • After minification 1.6 kB
  • After compression 821 B

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 851 B or 51% of the original size.

Image Optimization

-4%

Potential reduce by 10.6 kB

  • Original 286.8 kB
  • After minification 276.2 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. Marico images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 523.6 kB

  • Original 782.6 kB
  • After minification 778.6 kB
  • After compression 259.0 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 523.6 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (20%)

Requests Now

69

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marico. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

marico.co.za

marico.co.za

779 ms

Marico1.htm

Marico1.htm

412 ms

Marico2.htm

Marico2.htm

547 ms

Image4.jpg

Image4.jpg

273 ms

380 ms

Titel6.jpg

Titel6.jpg

631 ms

GM-Logo.jpg

GM-Logo.jpg

416 ms

MapRSA.jpg

MapRSA.jpg

497 ms

Telkom.jpg

Telkom.jpg

540 ms

RowOfPebbles.jpg

RowOfPebbles.jpg

541 ms

maps

maps

38 ms

swfobject.js

swfobject.js

525 ms

B2231_A30891_TGet.aspx

B2231_A30891_TGet.aspx

178 ms

LavenderHouse.jpg

LavenderHouse.jpg

729 ms

Molefe01.jpg

Molefe01.jpg

789 ms

embed

embed

383 ms

aw.aspx

aw.aspx

262 ms

js

js

68 ms

init_embed.js

init_embed.js

27 ms

560x120_social-woman_en_v2.gif

560x120_social-woman_en_v2.gif

101 ms

cm

cm

203 ms

map.js

map.js

250 ms

common.js

common.js

64 ms

map.js

map.js

65 ms

google4.png

google4.png

20 ms

overlay.js

overlay.js

20 ms

util.js

util.js

132 ms

onion.js

onion.js

95 ms

search_impl.js

search_impl.js

127 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

301 ms

stats.js

stats.js

132 ms

openhand_8_8.cur

openhand_8_8.cur

119 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

87 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

84 ms

kh

kh

150 ms

transparent.png

transparent.png

86 ms

uk_asso_GenericBanners_27-06-14_468x60.gif

uk_asso_GenericBanners_27-06-14_468x60.gif

58 ms

281 ms

kh

kh

155 ms

controls.js

controls.js

23 ms

kh

kh

121 ms

kh

kh

138 ms

kh

kh

130 ms

kh

kh

132 ms

kh

kh

137 ms

kh

kh

139 ms

kh

kh

134 ms

kh

kh

138 ms

kh

kh

141 ms

kh

kh

146 ms

kh

kh

143 ms

jquery.min.js

jquery.min.js

142 ms

css

css

127 ms

entity11.png

entity11.png

72 ms

vt

vt

110 ms

vt

vt

101 ms

vt

vt

99 ms

vt

vt

96 ms

vt

vt

96 ms

vt

vt

97 ms

vt

vt

117 ms

vt

vt

115 ms

vt

vt

116 ms

vt

vt

115 ms

vt

vt

117 ms

vt

vt

118 ms

vt

vt

135 ms

vt

vt

131 ms

vt

vt

119 ms

mapcnt6.png

mapcnt6.png

33 ms

tmapctrl.png

tmapctrl.png

35 ms

widget_call_home.js

widget_call_home.js

197 ms

map_v2_loading.png

map_v2_loading.png

130 ms

logo4-small.png

logo4-small.png

125 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

28 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

40 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

50 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

53 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

29 ms

Accessibility Review

marico.co.za accessibility score

33

Accessibility Issues

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

marico.co.za best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

marico.co.za SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Marico.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 Marico.co.za main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

marico.co.za

Open Graph description is not detected on the main page of Marico. 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: