31.7 sec in total
13.5 sec
18.1 sec
168 ms
Welcome to ebris.ru homepage info - get ready to check Ebris best content right away, or after learning these important things about ebris.ru
Visit ebris.ruWe analyzed Ebris.ru page load time and found that the first response time was 13.5 sec and then it took 18.3 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.
ebris.ru performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value13.9 s
0/100
25%
Value9.1 s
13/100
10%
Value2,210 ms
6/100
30%
Value0.028
100/100
15%
Value18.9 s
3/100
10%
13486 ms
838 ms
498 ms
517 ms
391 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ebris.ru, 36% (18 requests) were made to Reg.ru and 10% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (13.5 sec) belongs to the original domain Ebris.ru.
Page size can be reduced by 525.8 kB (70%)
754.5 kB
228.8 kB
In fact, the total size of Ebris.ru main page is 754.5 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. 25% of websites need less resources to load. CSS take 514.6 kB which makes up the majority of the site volume.
Potential reduce by 80.7 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 14.2 kB, which is 14% 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 80.7 kB or 80% of the original size.
Potential reduce by 0 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. Ebris images are well optimized though.
Potential reduce by 50.0 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 50.0 kB or 37% of the original size.
Potential reduce by 395.0 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. Ebris.ru needs all CSS files to be minified and compressed as it can save up to 395.0 kB or 77% of the original size.
Number of requests can be reduced by 33 (75%)
44
11
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ebris. 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 as a result speed up the page load time.
ebris.ru
13486 ms
ebris.ru
838 ms
all-styles.~76BF0A.css
498 ms
domain-shop-lot.~33A1BA.css
517 ms
shop-widget.~BC12B1.css
391 ms
modernizr.~47DAFF.js
411 ms
head-scripts.~336CED.js
401 ms
jquery-1.8.3.min.js
452 ms
all.~1A82D4.js
776 ms
domain-shop-lot.~62898A.js
553 ms
shop-widget.~7390E9.js
422 ms
conversion.js
30 ms
j.php
127 ms
analytics.js
139 ms
b-notify-browser.~A443C8.png
160 ms
b-please-wait.~43237B.gif
134 ms
b-header__logo_site_ru.svg
157 ms
b-popup__close.~2194E0.png
146 ms
regicons.~342F8A.woff
129 ms
v.gif
11 ms
ec.js
10 ms
collect
24 ms
collect
52 ms
ga-audiences
62 ms
watch.js
438 ms
fbevents.js
97 ms
authorize_tabs.~4210DC.js
144 ms
103 ms
smartPixel.min.js
2928 ms
code.js
672 ms
ping
829 ms
lot_recommendations
208 ms
rtrg
540 ms
collect
22 ms
b-dropdown.~4392E8.png
141 ms
90 ms
18 ms
advert.gif
85 ms
1
86 ms
counter
132 ms
4919539
86 ms
176 ms
raven.js
664 ms
json2.js
678 ms
postmessage.js
681 ms
jquery.cookie.js
695 ms
sleepyhead_in.js
699 ms
builder.js
133 ms
1379221
210 ms
collect
11 ms
ebris.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-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
ebris.ru 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
Missing source maps for large first-party JavaScript
ebris.ru 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
N/A
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ebris.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ebris.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.
ebris.ru
Open Graph description is not detected on the main page of Ebris. 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: