4.1 sec in total
391 ms
3.6 sec
155 ms
Click here to check amazing O 1 content for Russia. Otherwise, check out these important facts you probably never knew about o1.ru
Доставка товаров по европейским каталогам
Visit o1.ruWe analyzed O1.ru page load time and found that the first response time was 391 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
o1.ru performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value1.7 s
99/100
25%
Value2.2 s
99/100
10%
Value0 ms
100/100
30%
Value0.011
100/100
15%
Value1.4 s
100/100
10%
391 ms
478 ms
122 ms
470 ms
472 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 51% of them (29 requests) were addressed to the original O1.ru, 21% (12 requests) were made to Vk.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Vk.com.
Page size can be reduced by 382.8 kB (71%)
537.1 kB
154.2 kB
In fact, the total size of O1.ru main page is 537.1 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. 40% of websites need less resources to load. Javascripts take 346.5 kB which makes up the majority of the site volume.
Potential reduce by 23.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 4.8 kB, which is 15% 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 23.2 kB or 73% of the original size.
Potential reduce by 3.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. O 1 images are well optimized though.
Potential reduce by 261.1 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 261.1 kB or 75% of the original size.
Potential reduce by 94.8 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. O1.ru needs all CSS files to be minified and compressed as it can save up to 94.8 kB or 82% of the original size.
Number of requests can be reduced by 25 (49%)
51
26
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
o1.ru
391 ms
www.o1.ru
478 ms
core.css
122 ms
jquery.fancybox.css
470 ms
style.css
472 ms
template_styles.css
497 ms
core.js
646 ms
core_ajax.js
597 ms
session.js
597 ms
jquery-1.11.0.min.js
777 ms
jquery.fancybox.pack.js
596 ms
script.js
595 ms
script.js
687 ms
css
24 ms
cloud-zoom.1.0.2.min.js
687 ms
jquery.tooltipster.min.js
691 ms
tooltipster.css
688 ms
mobile.css
743 ms
jquery.sticky.js
808 ms
openapi.js
699 ms
openapi.js
1525 ms
personal-icon.png
96 ms
logo.png
97 ms
contacts-icons.gif
96 ms
search-ico.png
101 ms
top_euroshops.gif
190 ms
sound_on.gif
106 ms
msNrBgwx3ln3jjNy5b_Syw.ttf
57 ms
kTYfCWJhlldPf5LnG4ZnHC3USBnSvpkopQaUR-2r7iU.ttf
73 ms
paysystems.png
92 ms
up-arr.png
91 ms
footer-icons.gif
91 ms
upload.gif
119 ms
widget_community.php
282 ms
online-consultant.png
94 ms
watch.js
1 ms
hit
258 ms
analytics.js
24 ms
short-user-reg.php
122 ms
collect
19 ms
loader_nav19239_3.js
120 ms
lite.css
118 ms
lite.js
468 ms
lang3_0.js
354 ms
widget_community.css
238 ms
xdm.js
239 ms
al_community.js
240 ms
hit
129 ms
SByIY0MCs88.jpg
259 ms
G8gV_a7kzIc.jpg
373 ms
dlUtddPX_w0.jpg
375 ms
EXxOXMyvPVg.jpg
371 ms
xpFdgtTJYBU.jpg
386 ms
iZRiNj83nAY.jpg
375 ms
x1uXflFsZXo.jpg
263 ms
camera_50.png
122 ms
w_logo.png
118 ms
o1.ru accessibility score
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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
o1.ru 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
o1.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise O1.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that O1.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
o1.ru
Open Graph description is not detected on the main page of O 1. 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: