5.4 sec in total
325 ms
4.8 sec
315 ms
Click here to check amazing Erarta content for Russia. Otherwise, check out these important facts you probably never knew about erarta.com
Эрарта — крупнейший частный музей современного искусства в России. В Санкт-Петербурге российское современное искусство представлено на 5 этажах музея.
Visit erarta.comWe analyzed Erarta.com page load time and found that the first response time was 325 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
erarta.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value13.2 s
0/100
25%
Value8.8 s
16/100
10%
Value1,930 ms
8/100
30%
Value0.217
57/100
15%
Value14.7 s
8/100
10%
325 ms
817 ms
250 ms
252 ms
386 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 75% of them (69 requests) were addressed to the original Erarta.com, 4% (4 requests) were made to Mc.yandex.ru and 3% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Erarta.com.
Page size can be reduced by 1.2 MB (45%)
2.6 MB
1.5 MB
In fact, the total size of Erarta.com main page is 2.6 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 89.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. 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 89.2 kB or 82% of the original size.
Potential reduce by 98.4 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. Erarta images are well optimized though.
Potential reduce by 637.3 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 637.3 kB or 67% of the original size.
Potential reduce by 366.3 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. Erarta.com needs all CSS files to be minified and compressed as it can save up to 366.3 kB or 84% of the original size.
Number of requests can be reduced by 52 (60%)
86
34
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Erarta. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
erarta.com
325 ms
www.erarta.com
817 ms
jquery.colorbox.css
250 ms
pagination.css
252 ms
style_el.css
386 ms
main.css
622 ms
pagination-messages.js
265 ms
jquery.js
489 ms
jquery.colorbox.js
495 ms
jquery.colorbox.init.js
378 ms
jquery.pagination.js
406 ms
pagination.js
512 ms
jquery-1.7.2.js
781 ms
main-start.js
1314 ms
browserAutocompleteListener.js
657 ms
all.js
79 ms
print-version.js
425 ms
logo.png
167 ms
vk.png
167 ms
fb.png
166 ms
twitter.png
167 ms
ru.gif
168 ms
en.png
164 ms
search-btn.jpg
271 ms
trans.gif_2095637534.gif
273 ms
museum.png
518 ms
Erarta_exhibitions_header.jpg
390 ms
Erarta_calendar_header.jpg
393 ms
Erarta_visitors_header.jpg
401 ms
Erarta_buying_art_header.jpg
532 ms
Erarta_ga_main01ru.jpg
1183 ms
Erarta_genezis_main.jpg
643 ms
Erarta_khlebnikov_main1.png
784 ms
Erarta_polozkova_main.jpg
798 ms
Erarta_tricky_main1.jpg
875 ms
Erarta_restnew_main.jpg
784 ms
Love_art_logo.png
774 ms
main_museum.jpg
1148 ms
Erarta_buying_art_main.jpg
1157 ms
Erarta_calendar_main.jpg
1277 ms
Erarta_visitors_main.jpg
1187 ms
Erarta_support_project2_main_bottom.png
1006 ms
Erarta_medals.png
1257 ms
logo_pink.jpg
1279 ms
main-nav-separator.jpg
1284 ms
DINPro-Regular.woff
1481 ms
cart.png
1303 ms
Erarta-head-gray-main.jpg
1976 ms
Erarta-head-main.jpg
2468 ms
red-close.png
1390 ms
DINPro-Bold.woff
1527 ms
corner_red.png
1433 ms
icon_museum.png
1491 ms
128 ms
xd_arbiter.php
92 ms
xd_arbiter.php
168 ms
HFcuAd9WdIQ
186 ms
instagramm.png
288 ms
kudaGo_footer.jpg
517 ms
watch.js
185 ms
ga.js
62 ms
icon_galleries.png
1431 ms
icon_programmes.png
1455 ms
icon_design.png
1599 ms
up_small.png
1597 ms
advertisement.png
1602 ms
report.png
1580 ms
inpage_linkid.js
10 ms
__utm.gif
12 ms
collect
69 ms
xd_arbiter.php
41 ms
www-embed-player-vflZsBgOl.css
68 ms
www-embed-player.js
89 ms
base.js
162 ms
museum_news.png
1609 ms
down_small.png
1620 ms
watch.js
430 ms
corner.jpg
1504 ms
vk.jpg
1509 ms
facebook.jpg
1609 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
48 ms
ad_status.js
47 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
94 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
106 ms
youtube.png
1509 ms
twitter.jpg
1496 ms
feedback.png
1394 ms
advert.gif
84 ms
mobile.png
1346 ms
close.png
1355 ms
bullets.png
1366 ms
1
85 ms
erarta.com 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
erarta.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
erarta.com 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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Erarta.com 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 Erarta.com 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.
erarta.com
Open Graph description is not detected on the main page of Erarta. 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: