9.3 sec in total
468 ms
5.8 sec
3 sec
Click here to check amazing Arch content. Otherwise, check out these important facts you probably never knew about arch.by
Arch.by — независимый социальный проект, рассказывающий о развитии архитектуры Минска со времен первой фотографии до наших дней. Любой может загружать исторически-значимые фотографии города, указывать...
Visit arch.byWe analyzed Arch.by page load time and found that the first response time was 468 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
arch.by performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value13.5 s
0/100
25%
Value15.6 s
0/100
10%
Value1,320 ms
17/100
30%
Value0
100/100
15%
Value14.3 s
9/100
10%
468 ms
143 ms
240 ms
224 ms
375 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 64% of them (23 requests) were addressed to the original Arch.by, 17% (6 requests) were made to Api-maps.yandex.ru and 6% (2 requests) were made to Vec01.maps.yandex.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Vec03.maps.yandex.net.
Page size can be reduced by 173.9 kB (38%)
460.4 kB
286.5 kB
In fact, the total size of Arch.by main page is 460.4 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 236.7 kB which makes up the majority of the site volume.
Potential reduce by 13.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 13.5 kB or 75% of the original size.
Potential reduce by 26 B
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. Arch images are well optimized though.
Potential reduce by 75.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 75.7 kB or 71% of the original size.
Potential reduce by 84.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. Arch.by needs all CSS files to be minified and compressed as it can save up to 84.8 kB or 85% of the original size.
Number of requests can be reduced by 5 (15%)
33
28
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Arch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
arch.by
468 ms
style.css
143 ms
mootools-core.js
240 ms
arch.js
224 ms
index.xml
375 ms
map.yandex.clusterer.js
212 ms
watch.js
0 ms
index.xml
598 ms
_YMaps.css
117 ms
_YMaps.js
473 ms
archby_logo.png
218 ms
button.png
112 ms
6eb4207bd5f527f23dcc17e962ed3fe1d760b14c.jpg
635 ms
0c68296f47952fd163da74911fb4e4dbd748582e.jpg
284 ms
2922764b56bf46689177a556f84493f3d35287c7.jpg
110 ms
31edc8229945937c1d7c87507bb478a7f0aaff44.jpg
449 ms
8c7d961555096a0486b8ed2b2efd6258c3f6c84c.jpg
567 ms
ba79afbb6d7a14c0d1d22d6e3761718048947b3a.jpg
566 ms
1c518fc3e8d768ce324ad2a9640da629b1ad3a1e.jpg
594 ms
2db0df5b77f80688c69e4597b2d76d6a252fa22e.jpg
594 ms
904f6088948d98aedc4351ababa5607e3126bad3.jpg
615 ms
545047d21f66f5b57f2c1170e0790a5b5e67dc93.jpg
613 ms
ussr-envelope.jpg
592 ms
add.png
535 ms
VintagePhotos.jpg
559 ms
rss.png
557 ms
tiles
1226 ms
tiles
1551 ms
tiles
1222 ms
tiles
1548 ms
objects-on-map
433 ms
mics.png
689 ms
tiles
734 ms
tiles
714 ms
554 ms
photo1.png
153 ms
arch.by accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
arch.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
arch.by SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Arch.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 Arch.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.
arch.by
Open Graph data is detected on the main page of Arch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: