8 sec in total
511 ms
6.9 sec
555 ms
Click here to check amazing Freedom Cgr content for Japan. Otherwise, check out these important facts you probably never knew about freedomcgr.com
Visit freedomcgr.comWe analyzed Freedomcgr.com page load time and found that the first response time was 511 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
freedomcgr.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.006
100/100
15%
Value0
0/100
10%
511 ms
552 ms
322 ms
336 ms
531 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 58% of them (53 requests) were addressed to the original Freedomcgr.com, 22% (20 requests) were made to Static.xx.fbcdn.net and 15% (14 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Freedomcgr.com.
Page size can be reduced by 231.7 kB (17%)
1.4 MB
1.2 MB
In fact, the total size of Freedomcgr.com main page is 1.4 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 450 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 450 B or 54% of the original size.
Potential reduce by 44.8 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. Freedom Cgr images are well optimized though.
Potential reduce by 185.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 185.4 kB or 78% of the original size.
Potential reduce by 1.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. Freedomcgr.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 66% of the original size.
Number of requests can be reduced by 22 (25%)
89
67
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freedom Cgr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
freedomcgr.com
511 ms
www.freedomcgr.com
552 ms
home_top.html
322 ms
home_left.html
336 ms
home_main.html
531 ms
logo01.jpg
319 ms
spacer.gif
333 ms
home-bunner.jpg
664 ms
topics-w.jpg
338 ms
information-b.jpg
352 ms
gakkifea-b.jpg
559 ms
tsp-b.jpg
644 ms
home-w.jpg
627 ms
guitarsbasses-b.jpg
635 ms
gallery-b.jpg
670 ms
colorchart-b.jpg
864 ms
effectors-b.jpg
937 ms
parts-b.jpg
938 ms
pickups-b.jpg
963 ms
accessories-b.jpg
958 ms
repair-b.jpg
1013 ms
aboutus-b.jpg
1191 ms
dealers-b.jpg
1261 ms
links-b.jpg
1263 ms
recruiltop-b.jpg
1274 ms
arimozo-b.jpg
1289 ms
youtube2.gif
1324 ms
fi.jpg
1521 ms
lightbox.css
1557 ms
prototype.js
2650 ms
scriptaculous.js
1566 ms
lightbox.js
1729 ms
effects.js
669 ms
builder.js
352 ms
iframe_api
50 ms
topic_main.html
339 ms
160301_dulakeliberoflat_top_B.jpg
1828 ms
dulake_libero12.jpg
1181 ms
dulake_flat12.jpg
1509 ms
topics-1.jpg
722 ms
topics-2.jpg
952 ms
topics-3.jpg
952 ms
topics-4.jpg
1056 ms
topics-5.jpg
1309 ms
topics-6.jpg
1174 ms
topics-7.jpg
1386 ms
topics-8.jpg
1484 ms
topics-9.jpg
1672 ms
topics-10.jpg
1797 ms
topics-11.jpg
1886 ms
topics-12.jpg
1943 ms
facebook-top.jpg
1834 ms
loading.gif
2030 ms
closelabel.gif
2126 ms
www-widgetapi.js
31 ms
likebox.php
278 ms
kyEKgjk51ZE.css
170 ms
xgj7bXhJNEH.css
211 ms
Czh0gDTFcBt.css
254 ms
N-k91nHCZS2.css
330 ms
ZeuPykSxSED.css
337 ms
1kPfZUdGrka.js
335 ms
Yuj_Y8xNH2C.js
373 ms
Mpe38fuBVZ2.js
291 ms
n8qIhCw3vMx.js
290 ms
QKy94bWvcbp.js
371 ms
6q5od22S-uf.js
370 ms
7B-2ZS3Qt8r.js
405 ms
qcMicXoOToy.js
450 ms
57RpJa05x58.js
410 ms
10365899_807340706044185_8188847131738075253_n.jpg
254 ms
safe_image.php
248 ms
74723_292924230819171_1603858564_n.jpg
278 ms
1017418_836457456465843_3162756878173895191_n.jpg
395 ms
971594_836457413132514_1268300336788363580_n.jpg
361 ms
1391515_836457433132512_6197024352336806200_n.jpg
359 ms
1558527_836457419799180_6220376014486675179_n.jpg
362 ms
10570317_835688013209454_7772090018350175080_n.jpg
399 ms
941915_835688513209404_4329547792156041165_n.jpg
396 ms
1913526_835680303210225_128639032404994591_n.jpg
435 ms
1422519_835680846543504_5867279932170707857_n.jpg
437 ms
12227598_835188816592707_7161075051330497108_n.jpg
477 ms
10405240_835188809926041_6813558628658171245_n.jpg
435 ms
1802_835188806592708_6174730325691619411_n.jpg
437 ms
10338768_835188976592691_7515837934201985719_n.jpg
437 ms
wL6VQj7Ab77.png
95 ms
s7jcwEQH7Sx.png
96 ms
QDwYpIaRyfG.png
96 ms
K00K-UgnsKu.png
97 ms
VXcANLwwL5J.js
43 ms
AmlxWlqMvlv.js
44 ms
freedomcgr.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
freedomcgr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
freedomcgr.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freedomcgr.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Freedomcgr.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.
freedomcgr.com
Open Graph description is not detected on the main page of Freedom Cgr. 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: