9.5 sec in total
608 ms
8.7 sec
173 ms
Click here to check amazing Doraly content for Romania. Otherwise, check out these important facts you probably never knew about doraly.eu
Cumpara tot ceea ce ai nevoie dintr-un singur loc. Sute de mii de produse cu preturi mici atat la bucata cat si angro. Hai pe site si convinge-te!
Visit doraly.euWe analyzed Doraly.eu page load time and found that the first response time was 608 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
doraly.eu performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value20.4 s
0/100
25%
Value44.6 s
0/100
10%
Value60,840 ms
0/100
30%
Value0.003
100/100
15%
Value81.0 s
0/100
10%
608 ms
2266 ms
229 ms
460 ms
537 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Doraly.eu, 25% (29 requests) were made to Doraly.ro and 9% (11 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Doraly.ro.
Page size can be reduced by 1.4 MB (71%)
1.9 MB
564.3 kB
In fact, the total size of Doraly.eu main page is 1.9 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. 75% 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 1.3 MB
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 1.3 MB or 88% of the original size.
Potential reduce by 0 B
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. Doraly images are well optimized though.
Potential reduce by 92.6 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 92.6 kB or 41% of the original size.
Number of requests can be reduced by 70 (74%)
95
25
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doraly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
doraly.eu
608 ms
doraly.ro
2266 ms
bundle.min.css
229 ms
vue-file-agent.css
460 ms
css
537 ms
icon
788 ms
jquery.min.js
537 ms
jquery.validate.min.js
720 ms
searchnode.prod.new.js
707 ms
OneSignalSDK.js
720 ms
email-decode.min.js
304 ms
vue.min.js
355 ms
axios.min.js
674 ms
lodash.min.js
525 ms
index.js
349 ms
pretty-checkbox-vue.min.js
276 ms
vue-file-agent.umd.js
342 ms
vee-validate.js
408 ms
index.js
272 ms
codemirror.min.js
341 ms
css.min.js
1473 ms
xml.min.js
406 ms
tether.min.js
407 ms
bootstrap.min.js
407 ms
validator.min.js
426 ms
jquery.bootpag.min.js
338 ms
cssbeautify.min.js
404 ms
materialize.min.js
441 ms
jquery.dotdotdot.min.js
404 ms
bootstrap-tokenfield.min.js
442 ms
expressCart.js
404 ms
select2.full.min.js
403 ms
slick.min.js
423 ms
icheck.min.js
439 ms
jquery.magnific-popup.min.js
1165 ms
jquery.sticky-kit.min.js
506 ms
modernizr-custom.js
1165 ms
hello.all.js
1177 ms
main.min.js
1163 ms
new-js.min.js
1175 ms
livrare-gratuita.min.js
1440 ms
pushy.min.js
1436 ms
jquery.scrolly.min.js
1462 ms
uc.js
1162 ms
v652eace1692a40cfa3763df669d7439c1639079717194
1458 ms
vue-select.css
212 ms
vue-select@latest
159 ms
http-vue-loader
813 ms
axios.min.js
1099 ms
vue-select.css
141 ms
vue-select@3.20.0
996 ms
http-vue-loader@1.4.2
994 ms
hotjar-862852.js
685 ms
tracker.js
1482 ms
gtm.js
684 ms
load.gif
697 ms
logo.svg
250 ms
200
963 ms
160
962 ms
300
963 ms
140
884 ms
SAL-PICTOGRAMA.png
962 ms
pictogramaSOL.png
961 ms
axios.min.js
229 ms
vue-select.js
396 ms
httpVueLoader.js
225 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf
302 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf
327 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX9-p7K4GLs.ttf
641 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX9-p7K4GLs.ttf
722 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf
721 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf
721 ms
fontawesome-webfont.woff
262 ms
App.vue
180 ms
968
1191 ms
modules.01a02f6e8b126e8c8358.js
1100 ms
conversion_async.js
1449 ms
analytics.js
1212 ms
1773 ms
spp.pl
1448 ms
fbevents.js
1201 ms
klaviyo.js
1162 ms
DKC.js
1986 ms
postmessage.js
1195 ms
1.js
1118 ms
js
567 ms
cc.js
825 ms
bc-v4.min.html
1335 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
1332 ms
e.js
1962 ms
f.html
2163 ms
widget.js
1739 ms
d.js
1890 ms
collect
500 ms
398166577477094
561 ms
399 ms
994 ms
collect
170 ms
tags
754 ms
ga-audiences
839 ms
,
246 ms
348 ms
tags
194 ms
cookie_get
191 ms
387 ms
pixel
207 ms
fledge-igmembership
625 ms
tag-v5.86.js
75 ms
lse1.0.html
84 ms
application-actions-f868d647724ad32bd77f8db7bb8b831d80d8b5de8c3123f0041fbaeb5265ea8c.js
79 ms
d.js
623 ms
events-1.6.0.min.js
181 ms
lse1.1.html
360 ms
cm
425 ms
bounce
47 ms
overlays-v5.86.js
17 ms
doraly.eu 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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role] values are not valid
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
doraly.eu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
doraly.eu 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
RO
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doraly.eu can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Doraly.eu 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.
doraly.eu
Open Graph data is detected on the main page of Doraly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: