18.1 sec in total
8.1 sec
9.7 sec
302 ms
Visit dillyeo.com now to see the best up-to-date Dillyeo content for United States and also check out these interesting facts you probably never knew about dillyeo.com
Visit dillyeo.comWe analyzed Dillyeo.com page load time and found that the first response time was 8.1 sec and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dillyeo.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value2.9 s
80/100
25%
Value2.9 s
95/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value2.9 s
96/100
10%
8107 ms
173 ms
81 ms
82 ms
83 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 89% of them (90 requests) were addressed to the original Dillyeo.com, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Verify.authorize.net. The less responsive or slowest element that took the longest time to load (8.1 sec) belongs to the original domain Dillyeo.com.
Page size can be reduced by 707.3 kB (56%)
1.3 MB
548.0 kB
In fact, the total size of Dillyeo.com main page is 1.3 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. 35% of websites need less resources to load. Javascripts take 692.3 kB which makes up the majority of the site volume.
Potential reduce by 36.2 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 12.5 kB, which is 28% 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 36.2 kB or 82% of the original size.
Potential reduce by 33.6 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. Dillyeo images are well optimized though.
Potential reduce by 528.5 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 528.5 kB or 76% of the original size.
Potential reduce by 109.0 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. Dillyeo.com needs all CSS files to be minified and compressed as it can save up to 109.0 kB or 83% of the original size.
Number of requests can be reduced by 67 (68%)
98
31
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dillyeo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
dillyeo.com
8107 ms
styles.css
173 ms
widgets.css
81 ms
aw_advancednewsletter.css
82 ms
styles.css
83 ms
grid.css
79 ms
slider.css
83 ms
product_onsale_label.css
116 ms
category_onsale_label.css
111 ms
aw_raf.css
112 ms
aitvbulletin.css
144 ms
subscribepopup.css
141 ms
jquery.fancybox.css
141 ms
jquery.fancybox.css
144 ms
prototype.js
328 ms
ccard.js
182 ms
validation.js
235 ms
builder.js
182 ms
effects.js
216 ms
dragdrop.js
206 ms
controls.js
283 ms
slider.js
215 ms
js.js
241 ms
form.js
259 ms
menu.js
259 ms
translate.js
270 ms
cookies.js
288 ms
jquery.min.js
365 ms
jquery.noconflict.js
293 ms
stepcarousel.js
301 ms
advancednewsletter.js
314 ms
ajaxcartpro.js
348 ms
cart.js
348 ms
sidebar.js
349 ms
form-contact.css
309 ms
seal.js
34 ms
topLinks.js
287 ms
skipLinks.js
290 ms
options.js
286 ms
wishlist.js
305 ms
miniWishlist.js
309 ms
addProductConfirmation.js
288 ms
removeProductConfirmation.js
287 ms
clickOnButtonInCartPageForm.js
295 ms
clickOnAddToCartInCategoryList.js
296 ms
clickOnAddToCartInOptionsPopup.js
293 ms
clickOnAddToCartInProductPage.js
284 ms
clickOnDeleteFromCart.js
287 ms
clickOnAddToCartInMiniWishlist.js
289 ms
product.js
296 ms
product.js
266 ms
onsale.js
262 ms
invite.js
279 ms
bundle.js
258 ms
jquery-1.7.1.min.js
257 ms
jquery.fancybox.js
262 ms
jquery.fancybox.js
275 ms
jquery.cookie.js
245 ms
modalwindow.js
264 ms
quickContact.js
264 ms
ga.js
7 ms
__utm.gif
28 ms
woopra.js
63 ms
bouttogetgeeky.jpg
428 ms
bnr_shopNowUsing_150x60.gif
64 ms
bg.jpg
95 ms
DillyLogo.png
50 ms
search_right.gif
49 ms
bkg_button_2.png
51 ms
grenademug_2.jpg
54 ms
swarovdblbrcltsilverclear_1000_1_.jpg
52 ms
opc-ajax-loader.gif
102 ms
al.gif
98 ms
submit.jpg
100 ms
close.jpg
103 ms
116 ms
top_links_divider.gif
137 ms
navi_bg.png
138 ms
menu_divider.gif
135 ms
top_shadow.gif
129 ms
fashion_heading_bg.gif
130 ms
fashion1.gif
140 ms
fashion2.gif
160 ms
fashion3.gif
161 ms
top_header.jpg
168 ms
slider_bg.jpg
164 ms
cart_shadow.png
152 ms
cart_bg.png
191 ms
cart_title.png
188 ms
subs_bg.png
185 ms
subs_btn.png
187 ms
footer_bg.png
207 ms
134 ms
secure90x72.gif
41 ms
left_arrow.jpg
133 ms
right_arrow.jpg
170 ms
like.php
214 ms
print.css
68 ms
Sh_BYjerrZ8.js
589 ms
LVx-xkvaJ0b.png
675 ms
__utm.gif
4 ms
dillyeo.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
dillyeo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
dillyeo.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 Dillyeo.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 Dillyeo.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.
dillyeo.com
Open Graph description is not detected on the main page of Dillyeo. 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: