14.8 sec in total
638 ms
13.3 sec
768 ms
Welcome to pervie.ru homepage info - get ready to check Pervie best content for Russia right away, or after learning these important things about pervie.ru
Поставщик продуктов питания с доставкой в рестораны, кафе, бары, гостиницы, офис и на дом. Онлайн заказы через наш интернет-магазин.
Visit pervie.ruWe analyzed Pervie.ru page load time and found that the first response time was 638 ms and then it took 14.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pervie.ru performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value15.0 s
0/100
25%
Value10.3 s
8/100
10%
Value13,260 ms
0/100
30%
Value0.959
3/100
15%
Value23.4 s
1/100
10%
638 ms
115 ms
213 ms
211 ms
215 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 88% of them (75 requests) were addressed to the original Pervie.ru, 4% (3 requests) were made to Google-analytics.com and 4% (3 requests) were made to Ringostat.com. The less responsive or slowest element that took the longest time to load (11.7 sec) belongs to the original domain Pervie.ru.
Page size can be reduced by 450.1 kB (51%)
885.2 kB
435.0 kB
In fact, the total size of Pervie.ru main page is 885.2 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. 45% of websites need less resources to load. Images take 386.3 kB which makes up the majority of the site volume.
Potential reduce by 68.5 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 37.9 kB, which is 49% 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 68.5 kB or 89% of the original size.
Potential reduce by 75.2 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, Pervie needs image optimization as it can save up to 75.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 237.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 237.7 kB or 70% of the original size.
Potential reduce by 68.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. Pervie.ru needs all CSS files to be minified and compressed as it can save up to 68.7 kB or 84% of the original size.
Number of requests can be reduced by 26 (33%)
78
52
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pervie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
pervie.ru
638 ms
index.css
115 ms
jquery-ui-1.10.4.custom.css
213 ms
jquery.fancybox.css
211 ms
jquery.ui.autocomplete.css
215 ms
jquery.min.js
340 ms
jquery-ui-1.10.4.custom.min.js
374 ms
jquery.cookie.js
334 ms
jquery.fancybox.pack.js
306 ms
jquery.maskedinput.js
334 ms
jquery.autocomplete.js
337 ms
target.js
409 ms
init_autocomplete.js
409 ms
referer2.js
410 ms
_index.js
411 ms
index.js
410 ms
jquery.form.js
410 ms
jquery.j2.message.js
481 ms
send_form.js
478 ms
login_form.js
486 ms
send_form.js
489 ms
send_form.js
503 ms
send_form.js
502 ms
change_amount.js
569 ms
send_form.js
571 ms
cambria.ttf
987 ms
46517dafb5f5fd9ebb15602aba12efcd_small.jpg
166 ms
13ec50b93ae8fcb4aa4a52fab907b3c9_small.jpg
161 ms
ffab2cbd7f190786ee69992af4c0e7ad_small.jpg
163 ms
b7ebd6ccd8f9696e939253fc560815ea_small.jpg
166 ms
fa03b55e9539cadf116353f1a2d018f0_small.jpg
167 ms
254e2a71b207e32c9c40052460f5f205_small.jpg
265 ms
d46f17c87b7a5ba62d82d91ccdee1bd2_small.jpg
266 ms
deeb097c44f2c0f3129c993dfa5b1229_small.jpg
264 ms
dacac28912827f6581aa60b5007e4679_small.jpg
263 ms
7623ffbb9ba0cf76d944a7e19cf2d780_small.jpg
266 ms
e74c369e109e1ded014a09bd520d82df_small.jpg
391 ms
e4e72aa9133ce783293886ccbd92a0c9_small.jpg
395 ms
5a4bf1dcc0781146bef507248a0e9f3c_small.jpg
392 ms
c590661feee6864fc1525f12ef81cd7d_small.jpg
401 ms
02a09251ee4f9728a0dac2f3deb7ac34_small.jpg
400 ms
9d8c689bffcc3d6f519372f62e5ded7d_small.jpg
524 ms
adbd05bf6db2b8eb9a80ff89268b3cf1_small.jpg
513 ms
e7323b29a8a62f667c22f18ff4c1dc29_small.jpg
552 ms
e2de26ec7fdfc88351974a1edaea4828_small.jpg
554 ms
e4d6225d249289e2dbd084d9c31a4003_small.jpg
554 ms
5ddf5326fc77ac7896d16d24f8b3a07d_small.jpg
644 ms
gtm.js
157 ms
bg.jpg
1139 ms
star_border.png
585 ms
pretzel.png
584 ms
basket_button.png
584 ms
top_menu_decor_left.png
682 ms
top_menu_decor_right.png
680 ms
magnifier.png
676 ms
bg_horeca.png
678 ms
crown.png
840 ms
like.png
847 ms
wave_white.png
844 ms
wave_white_in.png
845 ms
sheet.png
1175 ms
person.png
967 ms
minus.png
899 ms
plus.png
900 ms
arrow_pagin.png
897 ms
wave_line.png
1505 ms
blocks_top.png
1028 ms
watch.js
91 ms
blocks_center.png
933 ms
chili.png
1391 ms
pepper.png
1106 ms
blocks_bottom.png
1685 ms
cambria_b.ttf
2649 ms
analytics.js
152 ms
cambria_i.ttf
9581 ms
cambria_bi.ttf
11709 ms
wave_gray.png
1911 ms
loading.gif
2538 ms
linkid.js
50 ms
collect
23 ms
collect
188 ms
ringostat.min.js
1776 ms
ga-audiences
185 ms
getChangedNumber
513 ms
checkCallback
523 ms
pervie.ru 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-hidden="true"] elements contain focusable descendents
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.
[aria-*] attributes do not have valid values
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
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.
pervie.ru 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
pervie.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pervie.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Pervie.ru 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.
pervie.ru
Open Graph description is not detected on the main page of Pervie. 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: