2.7 sec in total
246 ms
2.3 sec
176 ms
Visit edgerecords.com now to see the best up-to-date Edgerecords content and also check out these interesting facts you probably never knew about edgerecords.com
Visit edgerecords.comWe analyzed Edgerecords.com page load time and found that the first response time was 246 ms and then it took 2.4 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.
edgerecords.com performance score
name
value
score
weighting
Value1.7 s
93/100
10%
Value2.7 s
85/100
25%
Value1.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.7 s
100/100
10%
246 ms
1168 ms
87 ms
23 ms
83 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Edgerecords.com, 91% (42 requests) were made to Hotmusicloops.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Hotmusicloops.com.
Page size can be reduced by 826.4 kB (51%)
1.6 MB
805.4 kB
In fact, the total size of Edgerecords.com main page is 1.6 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. Javascripts take 653.8 kB which makes up the majority of the site volume.
Potential reduce by 81.4 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 81.4 kB or 85% of the original size.
Potential reduce by 13.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. Edgerecords images are well optimized though.
Potential reduce by 423.1 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 423.1 kB or 65% of the original size.
Potential reduce by 308.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. Edgerecords.com needs all CSS files to be minified and compressed as it can save up to 308.1 kB or 86% of the original size.
Number of requests can be reduced by 28 (65%)
43
15
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edgerecords. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
edgerecords.com
246 ms
hotmusicloops.com
1168 ms
style.css
87 ms
js
23 ms
styles.css
83 ms
hml.css
138 ms
jquery.js
223 ms
jquery-migrate.min.js
98 ms
add-to-cart.min.js
104 ms
woocommerce-add-to-cart.js
124 ms
modernizr.js
187 ms
jquery.jplayer.min.2.7.1.js
249 ms
mp3-jplayer-2.3.2.js
207 ms
style.css
389 ms
jquery.form.min.js
53 ms
scripts.js
48 ms
jquery.blockUI.min.js
61 ms
woocommerce.min.js
93 ms
jquery.cookie.min.js
89 ms
cart-fragments.min.js
85 ms
jquery.shuffle.js
86 ms
smoothscroll.js
96 ms
controller.js
414 ms
core.min.js
132 ms
widget.min.js
132 ms
mouse.min.js
137 ms
slider.min.js
152 ms
jquery.ui.touch-punch.js
232 ms
wp-embed.min.js
193 ms
header-im.css
54 ms
wp-emoji-release.min.js
99 ms
logo@2.png
53 ms
bg.png
54 ms
sun-rays-570x450.jpg
282 ms
play.png
276 ms
sunny-days-570x450.jpg
283 ms
industrial-area-570x450.jpg
280 ms
coral-reefs-570x450.jpg
278 ms
seaside-fun-570x450.jpg
279 ms
lost-communication-570x450.jpg
277 ms
contemplation-570x450.jpg
280 ms
handstand-570x450.jpg
281 ms
dub-avenue-570x450.jpg
310 ms
icomoon.woff
457 ms
analytics.js
212 ms
collect
12 ms
edgerecords.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.
edgerecords.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
edgerecords.com 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 uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edgerecords.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 Edgerecords.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.
edgerecords.com
Open Graph description is not detected on the main page of Edgerecords. 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: