22.7 sec in total
491 ms
21.9 sec
301 ms
Visit office.by now to see the best up-to-date OFFICE content for Belarus and also check out these interesting facts you probably never knew about office.by
OFFICE.BY — интернет-магазин канцелярских товаров. Канцтовары, бумага А4, хозтовары, мебель с доставкой по Минску и всей РБ
Visit office.byWe analyzed Office.by page load time and found that the first response time was 491 ms and then it took 22.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
office.by performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value18.2 s
0/100
25%
Value10.7 s
7/100
10%
Value2,910 ms
3/100
30%
Value0.039
100/100
15%
Value15.3 s
7/100
10%
491 ms
710 ms
218 ms
328 ms
366 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 64% of them (48 requests) were addressed to the original Office.by, 7% (5 requests) were made to Google-analytics.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Office.by.
Page size can be reduced by 765.3 kB (13%)
6.1 MB
5.3 MB
In fact, the total size of Office.by main page is 6.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. 70% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 336.1 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 65.0 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 336.1 kB or 87% of the original size.
Potential reduce by 247.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. OFFICE images are well optimized though.
Potential reduce by 120.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 120.4 kB or 17% of the original size.
Potential reduce by 61.1 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.by needs all CSS files to be minified and compressed as it can save up to 61.1 kB or 34% of the original size.
Number of requests can be reduced by 31 (45%)
69
38
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OFFICE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
office.by
491 ms
office.by
710 ms
core.css
218 ms
main.popup.bundle.css
328 ms
page_3a35b7e892046c1f1e28f7188c31b870_v1.css
366 ms
template_349279bb87bbbeb40448cfe5a6e9e984_v1.css
886 ms
css
34 ms
core.js
553 ms
kernel_main_v1.js
572 ms
kernel_main_polyfill_customevent_v1.js
378 ms
dexie.bitrix.bundle.js
744 ms
core_ls.js
663 ms
core_frame_cache.js
686 ms
jquery-1.8.3.min.js
774 ms
ajax.js
907 ms
core_currency.js
1639 ms
main.popup.bundle.js
979 ms
d0427baa5f1f2d60b124560f805cfdb8_1.js
188 ms
template_7b3e7918b8d7c16d2d107c0cc50b12c1_v1.js
1361 ms
page_70b82b4f90374394d6b918af410f14c4_v1.js
977 ms
office.by
1924 ms
gtm.js
141 ms
form_loader.js
669 ms
logo_color.png
209 ms
5346ac41b9a873517cb7c3bdda20472a.png
208 ms
b7628159ed818310fc0e4925dd42002a.png
455 ms
2e5fb9e1a5203a9b3d687558d49285ac.png
454 ms
init
875 ms
icons_wish.png
457 ms
arrows.png
458 ms
bfdaece621181c19a61bf0b93090837c.png
677 ms
1f85c654095ec9ad2ae9775bc9651a89.png
834 ms
51f1a70d1c21357e77336ff9e4518db9.png
1545 ms
b6c03d99588d9282e544ad7780f8e603.png
1005 ms
6103477679b1d511df807addb37d74cc.png
19768 ms
5dfdea115fd13a8ff5eadb4f91fb28f8.png
2202 ms
58aed17b6e75243712c9252eee1fe57b.png
1225 ms
ba77c42faf4d4b183922b7fff56c0ff8.jpg
1808 ms
56a240fbba185253a8daacc6bcd8e0ca.jpg
1446 ms
zz-s.jpg
1556 ms
949fc7af1b8e0bb321ee37114400d7e3.jpg
1666 ms
c6e1bc5d1a745e2d6f17556627eed7fa.jpg
1667 ms
852d7c9455bdd4a53729d26b71550f91.jpg
1787 ms
e20b6854305ee343ffc7aaf32aa7f9ef.jpg
1776 ms
ff1a51ea63084c3a160f5f29b43c27c2.jpg
1886 ms
ebb6974c588710588faf14c851a34c5d.jpg
1908 ms
adcc54c02be6a5d8a44f103df9f1d84c.jpg
1921 ms
69faa8725405b78c8a75aa94a4dec70a.jpg
1996 ms
7e304f7e95728abbf22cbab09586be02.jpg
2030 ms
5442ea6425de348c666c620b25420f2a.jpg
2035 ms
subscribe_bg.png
2106 ms
sprite.svg
2149 ms
4iCs6KVjbNBYlgoKew7z.ttf
59 ms
4iCv6KVjbNBYlgoCjC3jtGyI.ttf
59 ms
4iCv6KVjbNBYlgoCxCvjtGyI.ttf
60 ms
js
89 ms
analytics.js
48 ms
tag.js
1080 ms
fbevents.js
194 ms
collect
184 ms
collect
203 ms
collect
181 ms
1089463874588451
86 ms
collect
19 ms
ga-audiences
97 ms
ga-audiences
157 ms
ajax.php
269 ms
collect
7 ms
loader_13.js
610 ms
ajax_counter.php
1229 ms
advert.gif
699 ms
app.js
506 ms
1
278 ms
collect
5 ms
1
282 ms
office.by 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
Image elements do not have [alt] attributes
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.
office.by 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
Missing source maps for large first-party JavaScript
office.by 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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Office.by 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 Office.by 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.
office.by
Open Graph data is detected on the main page of OFFICE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: