5.1 sec in total
48 ms
4.3 sec
805 ms
Click here to check amazing PREGO content for Ukraine. Otherwise, check out these important facts you probably never knew about prego.ua
Інтернет магазин взуття та сумок в Києві ✿ Взуття Prego ✿ Широкий асортимент брендового взуття та сумок за доступними цінами ➦ Доставка по Україні ☎ 38 (063) 721-40-69
Visit prego.uaWe analyzed Prego.ua page load time and found that the first response time was 48 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
prego.ua performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value7.9 s
3/100
25%
Value6.1 s
44/100
10%
Value2,480 ms
4/100
30%
Value0.938
3/100
15%
Value13.9 s
10/100
10%
48 ms
977 ms
48 ms
44 ms
25 ms
Our browser made a total of 189 requests to load all elements on the main page. We found that 9% of them (17 requests) were addressed to the original Prego.ua, 72% (136 requests) were made to Static.prego.ua and 7% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Static.prego.ua.
Page size can be reduced by 1.2 MB (40%)
2.9 MB
1.7 MB
In fact, the total size of Prego.ua main page is 2.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. 80% 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. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 260.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. This page needs HTML code to be minified as it can gain 49.4 kB, which is 17% 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 260.4 kB or 89% of the original size.
Potential reduce by 860.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. Obviously, PREGO needs image optimization as it can save up to 860.7 kB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 31.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.7 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. Prego.ua has all CSS files already compressed.
Number of requests can be reduced by 36 (23%)
160
124
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PREGO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
prego.ua
48 ms
prego.ua
977 ms
style.min.css
48 ms
blog.css
44 ms
main.css
25 ms
discount-archive.css
29 ms
validation.css
37 ms
popUp.css
272 ms
email-widget.css
45 ms
css
38 ms
css
53 ms
css
57 ms
all.css
35 ms
popup.css
10 ms
popup.css
16 ms
gtm.js
234 ms
login.svg
342 ms
cart.svg
318 ms
prego_logo_w.svg
312 ms
prego_logo_b.svg
316 ms
lupa.svg
312 ms
kievstar-black.svg
313 ms
header-sprite.png
372 ms
right.svg
585 ms
photo
581 ms
photo
580 ms
photo
578 ms
photo
578 ms
photo
599 ms
eyeactive.png
581 ms
Cart_Icon.svg
582 ms
photo
695 ms
photo
705 ms
photo
696 ms
photo
708 ms
photo
829 ms
photo
717 ms
photo
823 ms
photo
827 ms
photo
825 ms
photo
836 ms
photo
847 ms
photo
953 ms
photo
954 ms
photo
955 ms
photo
964 ms
photo
967 ms
photo
975 ms
photo
1088 ms
photo
1085 ms
photo
1082 ms
photo
1097 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
59 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
95 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff
170 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff
220 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff
222 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff
221 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
223 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff
223 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff
221 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8cLx1nejpA.woff
220 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Yzx1nejpA.woff
223 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8Rf21nejpA.woff
223 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nejpA.woff
224 ms
montserrat-bold.woff
1268 ms
sf-ui-display-bold.ttf
1381 ms
sf-ui-display-semibold.ttf
1580 ms
sf-ui-display-medium.woff
791 ms
sf-ui-display-light.ttf
1494 ms
sf-ui-display-ultralight-webfont.woff
1128 ms
js.min.js
132 ms
bonuses.js
102 ms
animation-and-requests.js
103 ms
jquery.cookie.min.js
189 ms
jquery.validate.min.js
187 ms
jquery.validate.unobtrusive.min.js
187 ms
prego.js
127 ms
msgwidget.css
101 ms
msgwidget.js
101 ms
api.js
207 ms
photo
772 ms
002rG3C3lLxnhwSnsTsKOAAAAAElFTkSuQmCC
1 ms
sNtlxyOi200b0AAAAASUVORK5CYII=
2 ms
Mf9A365092TJ4FtsAAAAASUVORK5CYII=
1 ms
AAAAAd0SU1FB+IDEAsiKWm0DMsAAABnSURBVBjTzdBHEoAwCEBRLNHYjTU2lPtf0pAsNJ7Av+JtYAYAUxBGMZkEI0kl2TJWXtCjsqKX6oanVinZGfUDqxqnaWY9G0DrxUpqE5ASTkJkEujV6mnztHs6APF0FxDx+tz7h+wvby8iGSICOqieAAAAAElFTkSuQmCC
1 ms
retag.js
96 ms
hotjar-2381451.js
103 ms
umdg85npazqhp33wmkhh.js
487 ms
montserrat-semibold.woff
1274 ms
photo
1045 ms
photo
1159 ms
photo
1175 ms
photo
1269 ms
photo
1311 ms
recaptcha__en.js
37 ms
photo
1298 ms
photo
1351 ms
21 ms
modules.8da33a8f469c3b5ffcec.js
23 ms
retar.php
460 ms
perform.php
538 ms
photo
1264 ms
photo
1269 ms
photo
1282 ms
photo
1304 ms
photo
1305 ms
photo
1256 ms
photo
1264 ms
photo
1277 ms
photo
1294 ms
photo
1301 ms
photo
1325 ms
photo
1256 ms
photo
1264 ms
photo
1278 ms
photo
1287 ms
photo
1297 ms
photo
1334 ms
photo
1255 ms
photo
1273 ms
photo
1275 ms
photo
1284 ms
photo
1273 ms
retar_js.php
94 ms
dd.php
508 ms
photo
1208 ms
photo
975 ms
photo
898 ms
photo
870 ms
photo
805 ms
photo
789 ms
photo
830 ms
photo
782 ms
photo
775 ms
photo
733 ms
photo
747 ms
photo
763 ms
photo
792 ms
photo
790 ms
photo
796 ms
photo
818 ms
photo
783 ms
photo
778 ms
photo
834 ms
photo
789 ms
photo
797 ms
photo
794 ms
photo
795 ms
photo
779 ms
photo
823 ms
photo
790 ms
photo
799 ms
photo
792 ms
photo
790 ms
photo
785 ms
photo
824 ms
photo
793 ms
photo
821 ms
photo
797 ms
photo
788 ms
photo
784 ms
photo
820 ms
photo
793 ms
photo
801 ms
photo
801 ms
photo
823 ms
photo
783 ms
photo
811 ms
photo
794 ms
photo
797 ms
photo
797 ms
photo
806 ms
photo
806 ms
photo
815 ms
photo
796 ms
photo
811 ms
photo
780 ms
photo
806 ms
photo
818 ms
bg-form.png
706 ms
mastercard.png
690 ms
viza__footer.png
675 ms
prego_logo_g.svg
674 ms
f1.svg
656 ms
viber.svg
664 ms
youtube.svg
587 ms
insta.svg
585 ms
tg.svg
562 ms
prego.ua 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-hidden="true"] elements contain focusable descendents
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
prego.ua best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
prego.ua 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
UK
UK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prego.ua can be misinterpreted by Google and other search engines. Our service has detected that Ukrainian is used on the page, and it matches the claimed language. Our system also found out that Prego.ua 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.
prego.ua
Open Graph data is detected on the main page of PREGO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: