5.7 sec in total
1 sec
4.2 sec
502 ms
Click here to check amazing Cayleys Corner content for South Africa. Otherwise, check out these important facts you probably never knew about cayleyscorner.com
I had the pleasure of getting some questions answered by the awesome Gory Artsick, formally known as Greg Allan, about the end of The Anti Retro Vinyls and the
Visit cayleyscorner.comWe analyzed Cayleyscorner.com page load time and found that the first response time was 1 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cayleyscorner.com performance score
1015 ms
223 ms
67 ms
79 ms
156 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 43% of them (66 requests) were addressed to the original Cayleyscorner.com, 18% (28 requests) were made to Widgets.itunes.apple.com and 6% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Cayleyscorner.com.
Page size can be reduced by 1.1 MB (50%)
2.3 MB
1.1 MB
In fact, the total size of Cayleyscorner.com main page is 2.3 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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 79.2 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 79.2 kB or 86% of the original size.
Potential reduce by 17.3 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. Cayleys Corner images are well optimized though.
Potential reduce by 927.4 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 927.4 kB or 70% of the original size.
Potential reduce by 114.9 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. Cayleyscorner.com needs all CSS files to be minified and compressed as it can save up to 114.9 kB or 83% of the original size.
Number of requests can be reduced by 92 (62%)
149
57
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cayleys Corner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.cayleyscorner.com
1015 ms
style.css
223 ms
css
67 ms
css
79 ms
flashblock.css
156 ms
player.css
153 ms
styles.css
156 ms
style.css
154 ms
lightbox.min.css
218 ms
shortcodes.css
313 ms
jquery.fancybox-1.3.4.css
257 ms
page_templates.css
247 ms
publisher.ad.min.js
122 ms
soundmanager2-nodebug-jsmin.js
302 ms
jquery.js
439 ms
jquery-migrate.min.js
297 ms
share_toolbar.js
207 ms
publisher.append.ad.min.js
53 ms
all.js
78 ms
jquery.cycle.all.min.js
324 ms
jquery.easing.1.3.js
273 ms
superfish.js
308 ms
custom.js
311 ms
mediaelementplayer.min.css
283 ms
wp-mediaelement.css
287 ms
jquery.form.min.js
350 ms
scripts.js
350 ms
wp-lightbox-2.min.js
443 ms
jquery.easing-1.3.pack.js
358 ms
jquery.fancybox-1.3.4.pack.js
445 ms
et-ptemplates-frontend.js
398 ms
wp-embed.min.js
417 ms
mediaelement-and-player.min.js
585 ms
wp-mediaelement.js
442 ms
wp-emoji-release.min.js
377 ms
share-medium.png
123 ms
footer-bottom-bg.png
191 ms
top-bg.png
197 ms
top-center-bg.jpg
444 ms
top-bottom-bg.png
492 ms
top-container-bg.png
406 ms
logo6.png
485 ms
left-menu-bg.png
392 ms
right-menu-bg.png
427 ms
content-menu-bg.png
427 ms
ajax-loader.gif
428 ms
AVRs-me1-306x191.jpg
444 ms
TrademrkLogo-306x191.jpg
448 ms
GunslingerInterview2-306x191.jpg
475 ms
featured-leftarrow.png
492 ms
featured-rightarrow.png
522 ms
main-area-bg.png
525 ms
main-top-shadow.png
557 ms
content-area.png
580 ms
content-area-top.png
581 ms
Gory-Artsick-200x200.jpg
581 ms
post-overlay.png
608 ms
AVRs-me1-200x200.jpg
608 ms
TrademrkLogo-200x200.jpg
642 ms
GunslingerInterview2-200x200.jpg
651 ms
AntiRetroVinyls1b-200x200.jpg
653 ms
controllerframe.html
24 ms
Gunslinger2b-200x200.jpg
632 ms
twitter.png
167 ms
facebook.png
207 ms
googleplus.png
207 ms
pinterest.png
207 ms
linkedin.png
231 ms
stumbleupon.png
232 ms
digg.png
368 ms
delicious.png
369 ms
Patterns-200x200.jpg
684 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
10 ms
EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff
18 ms
l5lwlGTN3pEY5Bf-rQEuIMvsW7MYFVYsuLRj6jSUyb0.woff
18 ms
AntiRetroVinyls1.jpg
681 ms
GunslingerBadBoy125.jpg
731 ms
controller.ad.min.js
15 ms
widget.html
115 ms
pages
51 ms
banner.html
44 ms
publisher.ad.min.js
35 ms
adjsframe.html
33 ms
tw.png
678 ms
readmore.png
650 ms
sidebar-bullet.png
649 ms
footer-main-bg.png
661 ms
frame.ad.min.js
33 ms
footer-pattern.png
660 ms
banner.min.css
30 ms
require.js
55 ms
piwik.js
336 ms
266 ms
xd_arbiter.php
108 ms
xd_arbiter.php
261 ms
piwik.js
249 ms
ajax-loader.gif
22 ms
slots
20 ms
footer-top-bg.png
649 ms
widget.css
44 ms
jquery.js
48 ms
handlebars.js
224 ms
underscore.js
45 ms
backbone.js
84 ms
bootstrap-typeahead.js
59 ms
itunes_item.js
59 ms
widget_templates.js
90 ms
widget.js
218 ms
jquery.tinyscrollbar.min.js
218 ms
web-storefront-preview.js
236 ms
web-storefront-base.js
219 ms
web-storefront-previewRegionSensitive.js
218 ms
itmsCheck.js
216 ms
banner-main-built.js
43 ms
slots
27 ms
footer-bullet.png
628 ms
lookup
118 ms
piwik.php
120 ms
like_box.php
107 ms
ebiMDO3r-8l.css
94 ms
jGc-59L_9lo.css
114 ms
q68gy-v_YMF.js
155 ms
FJmpeSpHpjS.js
179 ms
0wM5s1Khldu.js
173 ms
1bNoFZUdlYZ.js
173 ms
countries.json
27 ms
config.json
14 ms
en_US.json
11 ms
country-storeid.json
10 ms
ad-types.json
186 ms
60x60bb.jpg
176 ms
ajax-loader.gif
15 ms
header_itunes_store.png
8 ms
header_app_store.png
9 ms
background_generic.png
9 ms
background_itunes_top_payload.png
6 ms
icon_album.png
5 ms
btn_view.png
7 ms
background_scrollbar.png
19 ms
scrollbar_thumb.png
18 ms
footer.png
18 ms
11072720_793159674108494_8481218409641609934_n.jpg
240 ms
11825104_856779731079821_5571512957216256786_n.jpg
169 ms
11939732_827309960720751_8470211553845661100_n.jpg
122 ms
12573122_1034528453234792_2095907113404028526_n.jpg
95 ms
12003396_10203644101023307_9010451210718935130_n.jpg
94 ms
11846563_10205865529091531_7955479089137481172_n.jpg
176 ms
1915048_241477936192203_454434860966815192_n.jpg
121 ms
wL6VQj7Ab77.png
21 ms
s7jcwEQH7Sx.png
22 ms
sprites-web-storefront.png
18 ms
I6-MnjEovm5.js
21 ms
pQrUxxo5oQp.js
20 ms
featured-image-overlay.png
80 ms
cayleyscorner.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cayleyscorner.com 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), while the claimed language is English. Our system also found out that Cayleyscorner.com 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.
cayleyscorner.com
Open Graph description is not detected on the main page of Cayleys Corner. 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: