2.4 sec in total
300 ms
1.8 sec
302 ms
Click here to check amazing Carthage content. Otherwise, check out these important facts you probably never knew about carthage.co.za
Carthage is Web Company owned by James Mclaughlin, an internet professional based in Cape Town, South Africa
Visit carthage.co.zaWe analyzed Carthage.co.za page load time and found that the first response time was 300 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
carthage.co.za performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value9.3 s
1/100
25%
Value2.4 s
98/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value1.6 s
100/100
10%
300 ms
120 ms
186 ms
42 ms
728 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 97% of them (71 requests) were addressed to the original Carthage.co.za, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (728 ms) belongs to the original domain Carthage.co.za.
Page size can be reduced by 16.6 kB (3%)
617.6 kB
601.0 kB
In fact, the total size of Carthage.co.za main page is 617.6 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. 30% of websites need less resources to load. Images take 579.0 kB which makes up the majority of the site volume.
Potential reduce by 14.4 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 2.4 kB, which is 13% 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 14.4 kB or 79% 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. Carthage images are well optimized though.
Potential reduce by 34 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 2.1 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. Carthage.co.za needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 67% of the original size.
Number of requests can be reduced by 12 (17%)
72
60
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carthage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
carthage.co.za
300 ms
global.css
120 ms
splash.css
186 ms
ga.js
42 ms
bk.jpg
728 ms
logo.jpg
124 ms
b-clients.jpg
183 ms
b-stroke.jpg
188 ms
b-projects_f2.jpg
185 ms
b-case.jpg
187 ms
b-about.jpg
205 ms
b-fun.jpg
276 ms
b-contact.jpg
271 ms
blue-pages-diving.jpg
271 ms
jake-white-winning-way.jpg
282 ms
lewis-hough.jpg
293 ms
caperealty.jpg
357 ms
geosure.jpg
368 ms
fm-agency.jpg
365 ms
peter-eastman-prints.jpg
370 ms
sascoc.jpg
382 ms
decornation.jpg
443 ms
elite-paris.jpg
452 ms
eatcapetown.jpg
454 ms
freeline.jpg
453 ms
flybar.jpg
465 ms
os-outsource.jpg
521 ms
donna.jpg
530 ms
clinton-grobler-photography.jpg
534 ms
sirac.jpg
538 ms
human-works.jpg
550 ms
kalkan-exclusive-holidays.jpg
608 ms
cape-etc.jpg
617 ms
cds-global.jpg
624 ms
heath-nash.jpg
628 ms
highbury-safika-media.jpg
640 ms
synergy.jpg
697 ms
f-be.jpg
707 ms
f-last-fm.jpg
716 ms
f-twitter.jpg
719 ms
__utm.gif
13 ms
f-linked-in.jpg
646 ms
f-green.jpg
635 ms
f-orange.jpg
636 ms
b-clients_f2.jpg
93 ms
b-case_f2.jpg
95 ms
b-about_f2.jpg
96 ms
b-fun_f2.jpg
92 ms
b-ccontact_f2.jpg
97 ms
blue-pages-diving_f2.jpg
92 ms
jake-white-winning-way_f2.jpg
180 ms
lewis-hough_f2.jpg
181 ms
caperealty_f2.jpg
182 ms
geosure_f2.jpg
184 ms
fm-agency_f2.jpg
184 ms
peter-eastman-prints_f2.jpg
189 ms
sascoc_f2.jpg
271 ms
decornation_f2.jpg
271 ms
elite-paris_f2.jpg
271 ms
eatcapetown_f2.jpg
274 ms
freeline_f2.jpg
274 ms
flybar_f2.jpg
279 ms
os-outsource_f2.jpg
359 ms
donna_f2.jpg
359 ms
clinton-grobler-photography_f2.jpg
360 ms
sirac_f2.jpg
365 ms
human-works_f2.jpg
365 ms
kalkan-exclusive-holidays_f2.jpg
371 ms
cape-etc_f2.jpg
448 ms
cds-global_f2.jpg
449 ms
heath-nash_f2.jpg
450 ms
highbury-safika-media_f2.jpg
455 ms
synergy_f2.jpg
456 ms
carthage.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
Image elements do not have [alt] attributes
Links do not have a discernible name
carthage.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
carthage.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
Image elements do not have [alt] attributes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carthage.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 Carthage.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.
carthage.co.za
Open Graph description is not detected on the main page of Carthage. 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: