6.3 sec in total
586 ms
5.4 sec
345 ms
Welcome to office-world.ru homepage info - get ready to check Office World best content for Russia right away, or after learning these important things about office-world.ru
Купить офисное, банковское, торговое и оборудование для полиграфии с доставкой по Москве и России
Visit office-world.ruWe analyzed Office-world.ru page load time and found that the first response time was 586 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
office-world.ru performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value9.1 s
1/100
25%
Value8.9 s
15/100
10%
Value3,270 ms
2/100
30%
Value0.002
100/100
15%
Value11.0 s
21/100
10%
586 ms
908 ms
264 ms
281 ms
286 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 83% of them (121 requests) were addressed to the original Office-world.ru, 3% (4 requests) were made to Google-analytics.com and 1% (2 requests) were made to Kt.mixmarket.biz. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Office-world.ru.
Page size can be reduced by 1.3 MB (64%)
2.1 MB
739.2 kB
In fact, the total size of Office-world.ru main page is 2.1 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. 60% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 130.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 75.2 kB, which is 51% 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 130.2 kB or 88% of the original size.
Potential reduce by 70.1 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, Office World needs image optimization as it can save up to 70.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 948.4 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 948.4 kB or 77% of the original size.
Potential reduce by 189.5 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. Office-world.ru needs all CSS files to be minified and compressed as it can save up to 189.5 kB or 85% of the original size.
Number of requests can be reduced by 48 (35%)
137
89
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Office World. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
office-world.ru
586 ms
www.office-world.ru
908 ms
core.min.css
264 ms
core_popup.min.css
281 ms
style.css
286 ms
style.css
287 ms
style.css
286 ms
style.css
283 ms
style.css
422 ms
style.css
429 ms
style.css
433 ms
styles.css
435 ms
template_styles.css
568 ms
jquery.bxslider.css
437 ms
fancybox.css
552 ms
core.min.js
696 ms
core_fx.min.js
563 ms
core_ajax.min.js
563 ms
core_popup.min.js
564 ms
jquery.min.js
822 ms
fancybox-2.1.5.min.js
706 ms
jquery.ui.js
1112 ms
slider_price.js
741 ms
masonry.pkgd.min.js
706 ms
jquery.bxslider.min.js
843 ms
triumph.js
842 ms
filter.js
842 ms
jquery.history.js
878 ms
script.js
954 ms
script.js
958 ms
script.js
969 ms
_fn.js
971 ms
script.js
1015 ms
conversion.js
50 ms
cbh.js
483 ms
opensans.woff
487 ms
ba.js
389 ms
api.js
458 ms
gtm.js
111 ms
bg-head.png
365 ms
logo.png
369 ms
slogan.png
366 ms
searc-icon.png
370 ms
kelsonsans.woff
367 ms
PortalUser_09.png
648 ms
ent-bg.png
441 ms
ent_bg_but_too.png
438 ms
reg-bg.png
438 ms
cart_btn.png
441 ms
sc.png
436 ms
isq.png
556 ms
wel_img_1.png
556 ms
wel_img_2.png
556 ms
wel_img_3-1.png
552 ms
wel_img_4-1.png
557 ms
wel_img_5-1.png
553 ms
6f8d2145c26627e8b60051bd03565761.jpg
669 ms
28b6b8b82812371d7f743b091e945ed7.gif
667 ms
ed04ab11150cd517f61031669275c628.jpg
670 ms
7577f85bccd20c1cae6d24f178259d08.png
666 ms
02d332b26f71195e5ff814876d72452e.png
671 ms
8d2bfee00e7ad293f5e5e7a12aa8aa0a.jpg
668 ms
dfaa49e6ee1d32ccfc6ae8e8cda85f90.bmp
904 ms
no_photo.png
943 ms
f1f3f91174f67376ff409be020b7d1a5.png
900 ms
49a118ddb9b72ab6afbca99451085bb8.jpg
1819 ms
72fbab7fbdebff3a347acf80c9c36dad.jpg
900 ms
9dadec9e139214ef1870029909cd6ddb.jpg
902 ms
8ddda6d5919a2f0f90a63276a8918181.jpg
1076 ms
83b9c1fc82e57fa40f1daeb083aab567.gif
1074 ms
12b4113c72f4f78ce58e37e6855c517b.jpg
1078 ms
a127908dda72888721baabe38e33edc7.jpg
1076 ms
17b08fda49469d0214b839e62ff6f02c.jpg
1081 ms
0fd7c878f345e506997f16093240a255.jpg
1228 ms
3b9c48476ebc51dc48060050c5af8a99.jpg
1231 ms
rouble.otf
851 ms
339 ms
analytics.js
303 ms
am1294934011.js
1600 ms
watch.js
221 ms
rtrg
417 ms
support.js
461 ms
fbf0bc126d5cc87c06f29386a6f518e1.jpg
1018 ms
452650c21c372d5c0f199dd536edbc5a.gif
885 ms
8eb0e89b79f4dadf9c773ebef2bb9f8f.gif
900 ms
691cb28375afaf08dd4e5ec8a33b8435.gif
1010 ms
21f89fc8188c3274ea43f357d0961398.jpg
1007 ms
f5db6bd1cd7cc11f10fc16dc3c8ff59d.jpg
951 ms
b3603ce21d1f6d3ab7cac027f2a57d49.jpg
961 ms
dff85306e242146aeced16c989483ad9.gif
1098 ms
3f4355e3d3643784d47f0857b2446aaf.jpg
1096 ms
1cbe15311eb01b9ab4950819b4c92117.jpg
1096 ms
162 ms
bx_stat
378 ms
ec.js
63 ms
jsonp
288 ms
informer7.png
524 ms
06bfd12a574e68aea0be13a68cc0aced.gif
1009 ms
918055a5f510ff43430f38d7faeb9831.jpg
1012 ms
394c66e85e433475b686eb34d332e60b.png
1165 ms
b984942f7e660427803542ed8274956c.gif
1167 ms
aa1704623ad648491ccc8f863d93d4a3.png
1167 ms
68d5bc3f4e12290677a81686392522a9.gif
1173 ms
3fed48eef2b143134a50b9223a34bf3f.jpg
1187 ms
collect
40 ms
collect
127 ms
collect
68 ms
27eb3ea95a5e83028878cd4fe5c69a61.jpg
1321 ms
856ef44c6d9f655589ca39802a77ed78.gif
1184 ms
fb27754f20642916aee3ba0d315c86d7.gif
1181 ms
a94bd8957b5eb7ca0c1ccc6cd235323a.jpg
1191 ms
41401ed61a88b2f22d97ecb8cbfb4724.jpg
1208 ms
6ad0bc4d2f0d6735cbbc82447d85f4cc.gif
1300 ms
ga-audiences
45 ms
cf59912b957f0d518cde7cf9f6472944.gif
1092 ms
ea4c558bda9a8e3c59f3d865ee1853a4.gif
1091 ms
e9f2dda28951e4fb0af9c1d6b7859010.jpg
1100 ms
55b527f6c51df5d21d5d53e4e193b625.gif
1144 ms
d0c010fe09db2a79c5bee0d8fead1ce5.jpg
1217 ms
2b7c92822dd6265cb8d0a9947ffde8d3.png
1090 ms
974bd7771817c073e6f7ca304441d157.jpg
1092 ms
d6de28c4f18b1a0a5a3c2ff2571375bc.jpeg
1094 ms
7d689c26bb7c944ab80e46aaf14e0580.png
1093 ms
0a9d234b8a83ae269be9eaa182c32ed6.jpg
1155 ms
107663f37d81b99d77eeeccc41d754f9.gif
1077 ms
f5cbf172ea26fc01e64f970437447085.jpg
1079 ms
vk.png
1079 ms
yt.png
1082 ms
tw.png
950 ms
gp.png
1002 ms
phone.png
1088 ms
af_bef_how.png
1071 ms
quest.png
1066 ms
href_block.png
927 ms
point.png
932 ms
rss-logo.png
984 ms
cat_icon.png
1050 ms
sert.png
1076 ms
visa_foot.png
903 ms
logo_foot.png
905 ms
bx_loader.gif
911 ms
left-slide-nav.png
966 ms
trshower
512 ms
trshower
524 ms
right-slide-nav.png
1011 ms
office-world.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-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.
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
office-world.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
office-world.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
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Office-world.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 Office-world.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.
office-world.ru
Open Graph description is not detected on the main page of Office World. 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: