Tools & Wizards About Us
crank.co.za screenshot

Report Summary

  • 0

    Performance

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

crank.co.za

crank.co.za

Page Load Speed

14.2 sec in total

First Response

3.4 sec

Resources Loaded

10.6 sec

Page Rendered

237 ms

crank.co.za screenshot

About Website

Visit crank.co.za now to see the best up-to-date Crank content and also check out these interesting facts you probably never knew about crank.co.za

The Authority on South African Cycling

Visit crank.co.za

Key Findings

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

Performance Metrics

crank.co.za performance score

0

Network Requests Diagram

www.crank.co.za

3376 ms

style.css

526 ms

responsive.css

533 ms

custom.css

534 ms

jplayer.css

538 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 72% of them (64 requests) were addressed to the original Crank.co.za, 10% (9 requests) were made to Ajax.googleapis.com and 4% (4 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Crank.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 621.7 kB (69%)

Content Size

896.9 kB

After Optimization

275.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Crank.co.za main page is 896.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. Javascripts take 468.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 53.4 kB

  • Original 64.5 kB
  • After minification 53.6 kB
  • After compression 11.0 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 17% 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 53.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 81 B

  • Original 80.7 kB
  • After minification 80.6 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. Crank images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 326.3 kB

  • Original 468.3 kB
  • After minification 446.4 kB
  • After compression 142.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 326.3 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 241.9 kB

  • Original 283.4 kB
  • After minification 244.1 kB
  • After compression 41.5 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. Crank.co.za needs all CSS files to be minified and compressed as it can save up to 241.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (53%)

Requests Now

86

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.crank.co.za

www.crank.co.za

3376 ms

style.css

style.css

526 ms

responsive.css

responsive.css

533 ms

custom.css

custom.css

534 ms

jplayer.css

jplayer.css

538 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

542 ms

www.crank.co.za

www.crank.co.za

2106 ms

frontend_style.css

frontend_style.css

781 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

798 ms

comments.css

comments.css

821 ms

www.crank.co.za

www.crank.co.za

2295 ms

prototype.js

prototype.js

103 ms

scriptaculous.js

scriptaculous.js

114 ms

effects.js

effects.js

124 ms

lightbox.js

lightbox.js

1958 ms

jquery.js

jquery.js

2462 ms

jquery-migrate.min.js

jquery-migrate.min.js

1741 ms

upgrade.js

upgrade.js

1757 ms

superfish.js

superfish.js

2001 ms

hoverIntent.js

hoverIntent.js

2011 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

2241 ms

jquery.resize.end.js

jquery.resize.end.js

2279 ms

magpress_jquery.js

magpress_jquery.js

2278 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

2685 ms

selfhosted.js

selfhosted.js

2499 ms

jquery.fitvids.js

jquery.fitvids.js

2549 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

2543 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

2798 ms

frontend_script.js

frontend_script.js

2712 ms

social.js

social.js

2530 ms

wp-embed.min.js

wp-embed.min.js

2570 ms

reset.css

reset.css

2286 ms

clearfix.css

clearfix.css

2438 ms

social.css

social.css

2450 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

259 ms

builder.js

builder.js

11 ms

effects.js

effects.js

21 ms

dragdrop.js

dragdrop.js

21 ms

controls.js

controls.js

41 ms

slider.js

slider.js

32 ms

sound.js

sound.js

31 ms

lightbox.css

lightbox.css

254 ms

_gg8WTHBSRw

_gg8WTHBSRw

90 ms

59y7qwGB0ao

59y7qwGB0ao

140 ms

bern-banner-1.jpg

bern-banner-1.jpg

538 ms

crank.gif

crank.gif

563 ms

bulls-620x340.jpg

bulls-620x340.jpg

1336 ms

james2-620x340.jpg

james2-620x340.jpg

1499 ms

jayde-620x340.jpg

jayde-620x340.jpg

1188 ms

togh2-620x340.jpg

togh2-620x340.jpg

1319 ms

sam-620x340.jpg

sam-620x340.jpg

1551 ms

james4-190x120.jpg

james4-190x120.jpg

1118 ms

stage2-190x120.jpg

stage2-190x120.jpg

1475 ms

karl2-190x120.jpg

karl2-190x120.jpg

1716 ms

Rocky_Mountain_Banner2.jpg

Rocky_Mountain_Banner2.jpg

1575 ms

james4-100x80.jpg

james4-100x80.jpg

1624 ms

stage2-100x80.jpg

stage2-100x80.jpg

1741 ms

karl2-100x80.jpg

karl2-100x80.jpg

1750 ms

bulls-100x80.jpg

bulls-100x80.jpg

1812 ms

jayde-100x80.jpg

jayde-100x80.jpg

1828 ms

togh2-100x80.jpg

togh2-100x80.jpg

1914 ms

togh-100x80.jpg

togh-100x80.jpg

1974 ms

sam-100x80.jpg

sam-100x80.jpg

2007 ms

retrospec_banner.jpg

retrospec_banner.jpg

2009 ms

img_018-190x120.jpg

img_018-190x120.jpg

2077 ms

timthumb.php

timthumb.php

2111 ms

tr-190x120.jpg

tr-190x120.jpg

2265 ms

fb.jpg

fb.jpg

2258 ms

twitter.jpg

twitter.jpg

2289 ms

youtube.jpg

youtube.jpg

2290 ms

feed.jpg

feed.jpg

2334 ms

bern_ad.jpg

bern_ad.jpg

2383 ms

rss.png

rss.png

2514 ms

Cadence-Logo-300x240.jpg

Cadence-Logo-300x240.jpg

2543 ms

www-embed-player-vflRGs1ko.css

www-embed-player-vflRGs1ko.css

96 ms

www-embed-player.js

www-embed-player.js

118 ms

base.js

base.js

355 ms

sprite.png

sprite.png

2328 ms

_gg8WTHBSRw

_gg8WTHBSRw

81 ms

59y7qwGB0ao

59y7qwGB0ao

99 ms

sdk.js

sdk.js

8 ms

27 ms

xd_arbiter.php

xd_arbiter.php

21 ms

xd_arbiter.php

xd_arbiter.php

27 ms

base.js

base.js

41 ms

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

18 ms

ad_status.js

ad_status.js

18 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

56 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

67 ms

Accessibility Review

crank.co.za accessibility score

59

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

crank.co.za best practices score

77

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

crank.co.za SEO score

92

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crank.co.za can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Crank.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.

Social Sharing Optimization

crank.co.za

Open Graph data is detected on the main page of Crank. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: