15.9 sec in total
303 ms
15 sec
542 ms
Welcome to edredona.com homepage info - get ready to check Edredona best content right away, or after learning these important things about edredona.com
Visit edredona.comWe analyzed Edredona.com page load time and found that the first response time was 303 ms and then it took 15.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
edredona.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.6 s
34/100
25%
Value12.7 s
3/100
10%
Value2,890 ms
3/100
30%
Value0.008
100/100
15%
Value15.3 s
7/100
10%
303 ms
5281 ms
398 ms
409 ms
532 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 86% of them (114 requests) were addressed to the original Edredona.com, 9% (12 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Edredona.com.
Page size can be reduced by 257.8 kB (7%)
3.6 MB
3.4 MB
In fact, the total size of Edredona.com main page is 3.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. 50% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 221.0 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 221.0 kB or 87% of the original size.
Potential reduce by 3.0 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. Edredona images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 31.4 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. Edredona.com needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 16% of the original size.
Number of requests can be reduced by 94 (86%)
109
15
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edredona. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
edredona.com
303 ms
edredona.com
5281 ms
addify_csp_front_css.css
398 ms
theme.min.css
409 ms
custom-frontend-lite.min.css
532 ms
general.min.css
428 ms
eael-10894.css
431 ms
pa-global.min.css
481 ms
frontend.css
774 ms
woocommerce-layout.css
780 ms
woocommerce.css
791 ms
frontend.min.css
797 ms
style.min.css
846 ms
post-4.css
894 ms
frontend.min.css
1133 ms
swiper.min.css
1146 ms
custom-pro-frontend-lite.min.css
1158 ms
global.css
1294 ms
post-344.css
1206 ms
post-10894.css
1256 ms
post-92.css
1500 ms
ecs-style.css
1537 ms
post-316.css
1519 ms
post-10832.css
1571 ms
post-10947.css
1623 ms
post-11485.css
1653 ms
post-11650.css
1865 ms
post-12215.css
1890 ms
css
38 ms
wp-polyfill-inert.min.js
1899 ms
regenerator-runtime.min.js
1931 ms
wp-polyfill.min.js
2235 ms
hooks.min.js
2014 ms
w.js
17 ms
jquery.min.js
2362 ms
jquery-migrate.min.js
2260 ms
addify_csp_front_js.js
2281 ms
jquery.blockUI.min.js
2302 ms
add-to-cart.min.js
2382 ms
api.js
41 ms
client
58 ms
api.js
52 ms
custom-pro-widget-nav-menu.min.css
2495 ms
widget-theme-elements.min.css
2247 ms
widget-posts.min.css
2245 ms
custom-pro-widget-flip-box.min.css
2244 ms
eael-272.css
2306 ms
post-272.css
2277 ms
dashicons.min.css
2686 ms
all.min.css
2353 ms
v4-shims.min.css
2242 ms
photoswipe.min.css
2241 ms
default-skin.min.css
2304 ms
js.cookie.min.js
2272 ms
woocommerce.min.js
2500 ms
tracker.js
2270 ms
ecs_ajax_pagination.js
2323 ms
ecs.js
2327 ms
general.min.js
2409 ms
waypoints.min.js
2471 ms
lottie.min.js
2539 ms
TweenMax.min.js
2447 ms
pa-cursor.min.js
2307 ms
sourcebuster.min.js
2282 ms
order-attribution.min.js
2335 ms
underscore.min.js
2501 ms
wp-util.min.js
2339 ms
api-request.min.js
2321 ms
i18n.min.js
2421 ms
url.min.js
2400 ms
api-fetch.min.js
2387 ms
g.gif
19 ms
frontend.min.js
2275 ms
smush-lazy-load.min.js
2311 ms
hello-frontend.min.js
2296 ms
premium-wrapper-link.min.js
2383 ms
jquery.smartmenus.min.js
2319 ms
imagesloaded.min.js
2382 ms
eael-272.js
2296 ms
zxcvbn-async.min.js
2296 ms
password-strength-meter.min.js
2304 ms
webpack.runtime.min.js
2384 ms
frontend-modules.min.js
2471 ms
core.min.js
2384 ms
frontend.min.js
2366 ms
ecspro.js
2267 ms
webpack-pro.runtime.min.js
2224 ms
frontend.min.js
2306 ms
elements-handlers.min.js
2375 ms
jquery.sticky.min.js
2359 ms
jquery.zoom.min.js
2272 ms
jquery.flexslider.min.js
2291 ms
photoswipe.min.js
2396 ms
photoswipe-ui-default.min.js
2176 ms
add-to-cart-variation.min.js
2254 ms
single-product.min.js
2335 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
126 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
142 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
172 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
190 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
190 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
190 ms
KFOkCnqEu92Fr1Mu51xIIzc.ttf
189 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf
189 ms
KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf
191 ms
KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf
191 ms
KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf
190 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf
190 ms
Raleway-SemiBold.ttf
247 ms
Raleway-Bold.ttf
262 ms
Raleway-ExtraBold.ttf
257 ms
Raleway-Medium.ttf
260 ms
Raleway-Regular.ttf
261 ms
Raleway-SemiBold.ttf
2008 ms
CSM-HABANO-1.jpg
2602 ms
Raleway-Bold.ttf
2053 ms
Raleway-ExtraBold.ttf
2126 ms
PONQQ-Recuperado.jpg
2479 ms
SZ-TAUBE.jpg
2841 ms
EC-ROSS1.jpg
2799 ms
Raleway-Medium.ttf
2316 ms
Raleway-Regular.ttf
2377 ms
ESHR-JADE.jpg
3331 ms
CPI-LILA-LOGO.jpg
3377 ms
COBB1-MEGET-BLUE-LOGO.jpg
3253 ms
SB144-SERENITY-LOGO.jpg
2963 ms
ESHR-EDICION-1-scaled.jpg
3502 ms
Logo-Edredona.png
2998 ms
icono-mi-carrito.png
3179 ms
icono-mi-cuenta.png
3253 ms
recaptcha__en.js
24 ms
woocommerce-smallscreen.css
407 ms
zxcvbn.min.js
988 ms
edredona.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.
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
Links do not have a discernible name
edredona.com 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
edredona.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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edredona.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Edredona.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.
edredona.com
Open Graph description is not detected on the main page of Edredona. 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: