2.5 sec in total
213 ms
1.6 sec
750 ms
Click here to check amazing COMMUNITY RECORDS content for United States. Otherwise, check out these important facts you probably never knew about communityrecords.org
Visit communityrecords.orgWe analyzed Communityrecords.org page load time and found that the first response time was 213 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
communityrecords.org performance score
name
value
score
weighting
Value11.4 s
0/100
10%
Value18.8 s
0/100
25%
Value13.1 s
2/100
10%
Value9,880 ms
0/100
30%
Value1.001
2/100
15%
Value28.7 s
0/100
10%
213 ms
15 ms
79 ms
80 ms
80 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 72% of them (56 requests) were addressed to the original Communityrecords.org, 12% (9 requests) were made to S1.bcbits.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (658 ms) relates to the external source Scontent-dfw1-1.xx.fbcdn.net.
Page size can be reduced by 868.8 kB (22%)
3.9 MB
3.1 MB
In fact, the total size of Communityrecords.org main page is 3.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 65.9 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 65.9 kB or 85% of the original size.
Potential reduce by 222.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. COMMUNITY RECORDS images are well optimized though.
Potential reduce by 454.6 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 454.6 kB or 68% of the original size.
Potential reduce by 125.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. Communityrecords.org needs all CSS files to be minified and compressed as it can save up to 125.9 kB or 85% of the original size.
Number of requests can be reduced by 31 (42%)
73
42
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of COMMUNITY RECORDS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
communityrecords.org
213 ms
style.css
15 ms
billboard.css
79 ms
wpapp-styles.css
80 ms
styles.css
80 ms
frontend.css
81 ms
wp-paginate.css
81 ms
mootools-yui-compressed.js
77 ms
flower_core.js
79 ms
flower_init.js
143 ms
jquery.min.js
141 ms
jquery.easing.js
141 ms
billboard.min.js
178 ms
comment-reply.min.js
237 ms
jquery.form.min.js
238 ms
scripts.js
238 ms
wp-embed.min.js
255 ms
wp-emoji-release.min.js
294 ms
ga.js
177 ms
billboard_SXSW2.jpg
240 ms
288 ms
12347795_10153385414283512_537120563692876747_n.jpg
658 ms
tree.png
148 ms
tree_top.png
224 ms
doge.png
147 ms
Screen-Shot-2014-09-06-at-9.53.42-PM.png
147 ms
free_music_.png
145 ms
load.gif
144 ms
banner_web_1.jpg
220 ms
ShaunaDayTwo_one-300x300.jpg
148 ms
border_long.png
147 ms
woozyvid-compressed-300x300.png
219 ms
12794360_1125233114194249_2734631215805639257_n-300x300.jpg
218 ms
12813905_10153565783253512_3494657595723360579_n-300x300.jpg
218 ms
sxsw_2016_WEB-300x300.jpg
217 ms
12743873_10153538608653512_5945299918091350125_n-300x300.jpg
239 ms
ANTIGRAVITY-FEB2016-WEB_Page_26_Image_0001-768x512-1-300x300.jpg
241 ms
CRdogheadlogoBIG-copy-300x300.jpg
239 ms
8year_saleWEB-300x300.jpg
241 ms
250px_web_cover_safety.jpg
241 ms
250px_boyfriend_material.jpg
638 ms
all_people_learn_forget_repeat-250.jpg
246 ms
MWFC_billboard.jpg
235 ms
banner_innards_cc2.jpg
234 ms
weight_banner_31.jpg
234 ms
comp_banner_1.jpg
243 ms
donovan_banner_2.jpg
212 ms
banner_safety_new.jpg
239 ms
banner_billboard_redo_OUTNOW1.jpg
246 ms
skeletal_lightning_banner.jpg
242 ms
woozy_web_art_1800px-300x300.jpg
230 ms
250_dwolf_tape_cover.jpg
229 ms
tree_bottom.png
234 ms
OldSansBlack.ttf
88 ms
__utm.gif
61 ms
396 ms
communityrecords.org
142 ms
ajax-loader.gif
125 ms
jquery_bundle_min_136b3446a09d4fa9114e500420ddd113.js
167 ms
jquery_ui_bundle_min_eb87c6fdbddf6a772140ff3384426f34.js
163 ms
embedded_player_bundle_min_0c83dfdf1baca2a1a4121b94d1e56a74.js
216 ms
embedded_player_bundle_4b242053f812982a6e1bb85bb5d6904f.css
214 ms
embedded_player_v3_bundle_05f3276198d106b547493d179962640d.css
215 ms
v3_large_4549741cac3edd6a08024a9d63e62708.css
215 ms
slide-current.png
65 ms
slide.png
65 ms
playback-prev.png
65 ms
playback-pause.png
65 ms
playback-next.png
64 ms
ga.js
139 ms
quant.js
158 ms
embedplaypause.gif
78 ms
a1751905136_4.jpg
82 ms
_sprite-bc-embeds-20130528.png
53 ms
shortembed.gif
52 ms
__utm.gif
17 ms
collect
59 ms
pixel;r=1663623103;a=p-0207-dhLCDgvg;fpan=1;fpa=P0-1841870903-1458290699977;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458290699977;tzo=-180;ref=http%3A%2F%2Fcommunityrecords.org%2F;url=https%3A%2F%2Fbandcamp.com%2FEmbeddedPlayer.html%2Falbum%3D1959535012%2Fsize%3Dlarge%2Fbgcol%3Dffffff%2Flinkcol%3D333333%2Ftransparent%3Dtrue%2Fref%3Dhttp%25253A%25252F%25252Fcommunityrecords.org%25252F%2F;ogl=
53 ms
communityrecords.org 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
communityrecords.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
communityrecords.org SEO score
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Communityrecords.org 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 Communityrecords.org 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.
communityrecords.org
Open Graph description is not detected on the main page of COMMUNITY RECORDS. 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: