7.5 sec in total
415 ms
6.2 sec
895 ms
Click here to check amazing Kudd content for Canada. Otherwise, check out these important facts you probably never knew about kudd.ly
Buy quality and comfy home textiles at affordable prices: blankets, bedding, slippers, and accessories. For leisure and perfect sleep. Free delivery.
Visit kudd.lyWe analyzed Kudd.ly page load time and found that the first response time was 415 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
kudd.ly performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value23.2 s
0/100
25%
Value19.3 s
0/100
10%
Value7,560 ms
0/100
30%
Value0.776
5/100
15%
Value30.3 s
0/100
10%
415 ms
686 ms
92 ms
107 ms
552 ms
Our browser made a total of 167 requests to load all elements on the main page. We found that 66% of them (110 requests) were addressed to the original Kudd.ly, 5% (9 requests) were made to Fonts.gstatic.com and 5% (8 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Kudd.ly.
Page size can be reduced by 539.7 kB (56%)
966.1 kB
426.4 kB
In fact, the total size of Kudd.ly main page is 966.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% 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. HTML takes 548.3 kB which makes up the majority of the site volume.
Potential reduce by 441.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. This page needs HTML code to be minified as it can gain 69.7 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 441.0 kB or 80% of the original size.
Potential reduce by 98.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 98.7 kB or 24% of the original size.
Number of requests can be reduced by 144 (95%)
151
7
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kudd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 102 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.
kudd.ly
415 ms
www.kudd.ly
686 ms
uc.js
92 ms
js
107 ms
jquery.min.js
552 ms
jquery-migrate.min.js
515 ms
allow-webp-image-public.js
463 ms
lpadmin-public.js
311 ms
headerScript.min.js
463 ms
jquery.blockUI.min.js
345 ms
add-to-cart.min.js
589 ms
js.cookie.min.js
613 ms
woocommerce.min.js
725 ms
wp-backup-public.js
725 ms
woo-stamped.io-public.js
772 ms
analytics-talk-content-tracking.js
823 ms
wp-polyfill-inert.min.js
854 ms
regenerator-runtime.min.js
876 ms
wp-polyfill.min.js
1148 ms
hooks.min.js
994 ms
wpm-public.p1.min.js
1119 ms
js.cookie-2.1.3.min.js
1090 ms
jquery.bind-first-0.2.3.min.js
1117 ms
public.js
1227 ms
dtag.js
421 ms
7fcd9568-c168-4af5-8b4d-060efe8eecc7.js
100 ms
kuddly-33.js
1326 ms
js
164 ms
js
207 ms
1004843-10041487.js
164 ms
lib.js
162 ms
kuddly-10.js
1402 ms
tp.widget.bootstrap.min.js
33 ms
klaviyo.js
85 ms
23952.js
380 ms
tabby.js
1390 ms
tabby.polyfills.min.js
1145 ms
slick.min.js
1474 ms
caddy-public.js
1328 ms
sourcebuster.min.js
1581 ms
order-attribution.min.js
1573 ms
fd-script-frontend.js
1573 ms
gtm4wp-ecommerce-generic.js
1608 ms
gtm4wp-woocommerce.js
1609 ms
i18n.min.js
1689 ms
wc-blocks-google-analytics.js
1831 ms
slick.min.js
1754 ms
hoverIntent.min.js
1841 ms
01GYCCW03EJVW4VZYPJJFC53XP
102 ms
underscore.min.js
1937 ms
wp-util.min.js
1649 ms
main.min.js
1768 ms
frontend.min.js
1478 ms
frontend.js
1806 ms
swiper.js
1823 ms
tp.min.js
15 ms
bvselect.js
1641 ms
jquery.mCustomScrollbar.concat.min.js
1711 ms
main.js
1771 ms
navigation.js
1596 ms
widget.min.js
20 ms
owl.carousel.min.js
1833 ms
bootstrap.min.js
1812 ms
actions.js
1576 ms
kl-identify-browser.js
1565 ms
core.min.js
1736 ms
pum-site-scripts.js
1756 ms
add-to-cart-variation.min.js
1572 ms
frontend.min.js
1602 ms
frontend-pro.min.js
1802 ms
swiper-bundle.min.js
1836 ms
gtm.js
99 ms
scevent.min.js
65 ms
js
93 ms
bat.js
170 ms
js
229 ms
hmyhyuwjbk
226 ms
style.css
1552 ms
nb-sp.min.js
147 ms
style.min.css
1573 ms
allow-webp-image-public.css
1593 ms
js
112 ms
tfa.js
108 ms
core.js
200 ms
destination
105 ms
23952.js
20 ms
events.js
198 ms
rev.js
205 ms
toastr.min.css
1451 ms
caddy-premium-public.css
1484 ms
17227418.js
123 ms
clarity.js
102 ms
all.css
1686 ms
json
78 ms
slick.css
1378 ms
17227418
33 ms
caddy-public.css
1557 ms
caddy-icons.css
1401 ms
lpadmin-public.css
1424 ms
woocommerce-layout.css
1455 ms
0.7.22
31 ms
fender_analytics.739eafc699de20b4c3bb.js
37 ms
static.047f24ade89e4aff54a9.js
37 ms
runtime.f0f0482b9dd21f54d9ed.js
4 ms
sharedUtils.52f9c435f5e232af1a21.js
23 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js
25 ms
vendors~signup_forms~onsite-triggering.3bd60bc0c4ae67cf36d4.js
26 ms
vendors~signup_forms.50492d1c54f7e5a4075a.js
26 ms
default~signup_forms~onsite-triggering.ddf307d73959ae2a00ef.js
29 ms
signup_forms.5828d30d7aa945da8745.js
25 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js
37 ms
post_identification_sync.39cdd7baee564a8037ee.js
36 ms
tp2
35 ms
woocommerce.css
1673 ms
fd-style.css
1490 ms
slick.css
1464 ms
main.min.css
1584 ms
landing
46 ms
yith-quick-view.css
1550 ms
frontend.css
1572 ms
swiper.css
1569 ms
bvselect.css
1527 ms
style.css
1501 ms
main.css
1562 ms
custom.css
1546 ms
jquery.mCustomScrollbar.css
1459 ms
main2.css
1614 ms
product-sections-style.css
1577 ms
transitions.css
1431 ms
owl.carousel.min.css
1727 ms
elementor-fix.css
1519 ms
pum-site-styles.css
1555 ms
prettyPhoto.css
1327 ms
photoswipe.min.css
1346 ms
default-skin.min.css
1492 ms
style.css
1486 ms
frontend.min.css
1342 ms
wvs-theme-override.min.css
1342 ms
frontend-pro.min.css
1537 ms
wvs-pro-theme-override.min.css
1522 ms
kuddly-33.css
1502 ms
kuddly-10.css
1352 ms
font-awesome.min.css
1583 ms
swiper-bundle.min.css
1295 ms
logo-slider-wp-public.min.css
1585 ms
logo-slider-wp-public.js
1520 ms
photoswipe.min.js
1648 ms
photoswipe-ui-default.min.js
1375 ms
single-product.min.js
1364 ms
lazyload.min.js
1410 ms
cc-public-icons.ttf
1672 ms
komfies-grey-jpg.webp
1622 ms
komfies-pink.jpg.webp
1550 ms
css2
43 ms
index.svg
834 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff
69 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZs.woff
225 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZs.woff
226 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZs.woff
235 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZs.woff
232 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZs.woff
233 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZs.woff
235 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZs.woff
227 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZs.woff
234 ms
Recoleta-Regular.woff
1100 ms
arrow-right.svg
976 ms
css
47 ms
kudd.ly accessibility score
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
[role]s are not contained by their required parent element
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
Image elements do not have [alt] attributes
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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
kudd.ly 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
kudd.ly SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
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 Kudd.ly 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 Kudd.ly 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.
kudd.ly
Open Graph data is detected on the main page of Kudd. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: