6.5 sec in total
467 ms
2.4 sec
3.6 sec
Visit funky16corners.com now to see the best up-to-date Funky16 Corners content for United States and also check out these interesting facts you probably never knew about funky16corners.com
The best in funk, soul, jazz and rare groove vinyl
Visit funky16corners.comWe analyzed Funky16corners.com page load time and found that the first response time was 467 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
funky16corners.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value5.0 s
26/100
25%
Value3.3 s
91/100
10%
Value210 ms
89/100
30%
Value0.158
74/100
15%
Value5.8 s
66/100
10%
467 ms
139 ms
138 ms
142 ms
140 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 85% of them (56 requests) were addressed to the original Funky16corners.com, 5% (3 requests) were made to S.gravatar.com and 3% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Funky16corners.com.
Page size can be reduced by 534.4 kB (19%)
2.8 MB
2.2 MB
In fact, the total size of Funky16corners.com main page is 2.8 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 99.8 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 99.8 kB or 74% of the original size.
Potential reduce by 5.7 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. Funky16 Corners images are well optimized though.
Potential reduce by 341.7 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 341.7 kB or 64% of the original size.
Potential reduce by 87.3 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. Funky16corners.com needs all CSS files to be minified and compressed as it can save up to 87.3 kB or 66% of the original size.
Number of requests can be reduced by 30 (46%)
65
35
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funky16 Corners. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
funky16corners.com
467 ms
style.css
139 ms
rcol.css
138 ms
utils.js
142 ms
style.css
140 ms
dashicons.min.css
275 ms
desktop_style.css
274 ms
jetpack.css
417 ms
jquery.js
479 ms
jquery-migrate.min.js
281 ms
horizmenu.js
339 ms
front_end_script.js
414 ms
lightgrey.css
415 ms
wp-emoji-release.min.js
466 ms
addthis_widget.js
12 ms
devicepx-jetpack.js
15 ms
gprofiles.js
64 ms
wpgroho.js
276 ms
wp-embed.min.js
430 ms
e-201611.js
5 ms
jhs_pic.jpg
772 ms
new_funky16_logo.jpg
769 ms
jhs_higherground.jpg
748 ms
isaachayes_chains.jpg
750 ms
isaachayes_blackmoses_lp.jpg
748 ms
sssc_logo2.jpg
748 ms
recordbox.jpg
750 ms
decks.jpg
761 ms
gene_turntables.jpg
780 ms
harveyscales_pic.jpg
827 ms
harveyscales_whatsgood45.jpg
868 ms
angela_lp.jpg
788 ms
angela_label.jpg
882 ms
vantreose_pic.jpg
949 ms
vantreose_45_2.jpg
1041 ms
vantreose_45_1.jpg
1126 ms
f16_funkymusic.jpg
1169 ms
shalamar_12.jpg
1217 ms
lindajones_pic.jpg
1230 ms
lindajones_45.jpg
1221 ms
jimmyrobins_pic1.jpg
1389 ms
jimmyrobins_45.jpg
1406 ms
judyclay_youngbloods.jpg
1442 ms
judyclay_gettogether.jpg
1566 ms
lonettemckee_pic.jpg
1569 ms
lonette_45.jpg
1508 ms
soulguy_button.jpg
1525 ms
wrapperbg_lgrey.jpg
99 ms
headerbg_lgrey.jpg
99 ms
twitter.gif
734 ms
feed-icon-16x16.gif
735 ms
search_icon.gif
734 ms
header1.jpg
737 ms
dots.gif
735 ms
comment.gif
734 ms
category.gif
735 ms
tag.gif
735 ms
bullet.gif
736 ms
ironleg_button.jpg
736 ms
themocracy_icon.gif
737 ms
footerbg_lgrey.jpg
643 ms
hovercard.css
59 ms
services.css
60 ms
300lo.json
31 ms
sh.8e5f85691f9aaa082472a194.html
26 ms
g.gif
26 ms
funky16corners.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
<input type="image"> elements do not have [alt] text
funky16corners.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
funky16corners.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Funky16corners.com 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 Funky16corners.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.
funky16corners.com
Open Graph data is detected on the main page of Funky16 Corners. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: