6.4 sec in total
1.1 sec
4.7 sec
494 ms
Click here to check amazing I Prize content for Russia. Otherwise, check out these important facts you probably never knew about i-prize.ru
В магазине i-prize вы можете прямо сейчас заказать необычный подарок или удивительную вещь и уже завтра осчастливить себя и своих близких!
Visit i-prize.ruWe analyzed I-prize.ru page load time and found that the first response time was 1.1 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
i-prize.ru performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value13.0 s
0/100
25%
Value8.9 s
15/100
10%
Value730 ms
41/100
30%
Value0.013
100/100
15%
Value13.7 s
10/100
10%
1147 ms
41 ms
305 ms
368 ms
590 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 63% of them (62 requests) were addressed to the original I-prize.ru, 11% (11 requests) were made to I.siteapi.org and 8% (8 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain I-prize.ru.
Page size can be reduced by 455.6 kB (21%)
2.2 MB
1.8 MB
In fact, the total size of I-prize.ru main page is 2.2 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 88.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. 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 88.5 kB or 80% of the original size.
Potential reduce by 81.8 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. I Prize images are well optimized though.
Potential reduce by 58.0 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 58.0 kB or 29% of the original size.
Potential reduce by 227.4 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. I-prize.ru needs all CSS files to be minified and compressed as it can save up to 227.4 kB or 82% of the original size.
Number of requests can be reduced by 35 (36%)
96
61
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Prize. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
i-prize.ru
1147 ms
jquery-ui.css
41 ms
fancybox-4285c2a12e.css
305 ms
plugins-a8da77334f.css
368 ms
utils-af2dd981e6.css
590 ms
site-4a2ca7e245.css
654 ms
styles-f6e28003ca.css
549 ms
styles-7ea8995d39.css
619 ms
translate.js
674 ms
jquery.min.js
71 ms
jquery-ui.min.js
94 ms
global_libraries-3ef0d10230.js
1061 ms
site_library-b64e6223b8.js
1126 ms
global-91c8716e03.js
1028 ms
js
67 ms
6162613.oudep4ktgk.jpg
1416 ms
ga.js
40 ms
5464f2f39061c9cddb60f5d1a9038e395a74d8d6.JPG
572 ms
0.jpg
88 ms
5621189.djlcqaspeo.W215.jpg
323 ms
1.png
266 ms
29352853.cdit0tz2ao.W225.jpg
333 ms
21921311.5fokms6mw9.156x120.png
332 ms
31706168.q06jmlhtoy.156x120.png
267 ms
6403719.j4nucuxbql.156x120.jpg
737 ms
41854314.pb9zq2q7br.156x120.png
418 ms
12973693.ai3vyhxnh1.156x120.png
421 ms
6386152.5t5zdnc01i.156x120.png
771 ms
39621068.bgg7dmmm3x.156x120.png
482 ms
35062389.ey0zqawvd8.156x120.png
482 ms
30836813.kx2uynqwdz.156x120.png
734 ms
14756359.30hh1gtaom.156x120.png
579 ms
14369358.4n64kz15t8.156x120.png
799 ms
41166799.olhuocjn19.156x120.png
639 ms
36636127.kk0w95eqc6.156x120.png
738 ms
20081747.d1qo81nzi5.156x120.png
800 ms
35540477.hzmqezkkjl.156x120.png
892 ms
41865164.guux1sqd0o.156x120.png
893 ms
33179045.2auml7inw9.156x120.png
896 ms
26965516.nbexkzvadg.156x120.png
922 ms
26673214.jj1fq8o4s9.156x120.png
955 ms
34677420.3mjn1scxsm.156x120.png
955 ms
39735374.i1gsuoca8c.156x120.png
1051 ms
40125235.gljvlacjim.156x120.png
1050 ms
23409294.n6aa9iy40x.156x120.png
1053 ms
40248239.t2kvfe52sm.156x120.png
1073 ms
play.png
1112 ms
7935161.dtnwqx78f5.16x16.png
1113 ms
38325727.q7edfwumht.W120.jpg
1206 ms
0.jpg
257 ms
0.jpg
23 ms
0.jpg
76 ms
0.jpg
23 ms
0.jpg
106 ms
0.jpg
104 ms
0.jpg
51 ms
54a238df320520fc8f0d2eb7a4bf1654aecac5e4.jpg
400 ms
b2e71a46720bfb79b6bcb7ba8b35cf1ab97e253f.jpg
560 ms
3923cca69a039d553e952fb6e05d261053c05502.JPG
401 ms
769b47e1c554bfc7821344fb1511324ecfafd715.jpg
564 ms
d4fa670d5bdd4b2405d8251dd2b19fcd473b7bdb.jpg
564 ms
3b7ce5d9e490039d866501612de000d7b90ce332.jpg
712 ms
ea004cda86b4c94462dfeaab45012c3c8e287f52.jpg
717 ms
all.js
26 ms
__utm.gif
26 ms
jquery.min.js
188 ms
socnets-icons-big-66ce5768e1.png
1290 ms
watch.js
248 ms
2_left_s.png
1159 ms
2_center_s.png
1224 ms
2_right_s.png
1287 ms
3_left_s.png
1347 ms
FynCEbWh0w
301 ms
4ecd2b97705ad2568d80a1470950fd920df2e96f.jpg
638 ms
7dc5ffc24d0148020fdd5eeef7b4bb95f14b2a15.jpg
637 ms
a15990797b8fa7fd92064be63332083a400bfbdd.jpg
639 ms
3_center_s.png
1257 ms
3_right_s.png
1325 ms
get_image.png
1838 ms
suggest.js
40 ms
opensearch.js
31 ms
yandex-hint-rb.png
27 ms
1_left_s.png
1390 ms
1_center_s.png
1440 ms
1_right_s.png
1508 ms
watch.js
439 ms
6_left_s.png
1484 ms
6_center_s.png
1541 ms
widget_ru_RU.js
201 ms
6_right_s.png
1545 ms
30.png
1607 ms
33334332.r3nz4tkt6a.W958.jpg
1736 ms
36734371.2iv5v0dvvj.W958.jpg
1737 ms
34810227.5u785u19w2.W958.jpg
1546 ms
42600555.keowhtmqcc.W958.jpg
1769 ms
32647069.q8nl9pnfli.W958.jpg
1827 ms
advert.gif
85 ms
1
87 ms
i-prize.ru 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.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
i-prize.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
i-prize.ru SEO score
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-prize.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 I-prize.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.
i-prize.ru
Open Graph description is not detected on the main page of I Prize. 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: