259.7 sec in total
574 ms
242.9 sec
16.2 sec
Welcome to a-brick.ru homepage info - get ready to check A Brick best content for Russia right away, or after learning these important things about a-brick.ru
Данный сайт направлен на то, чтобы сделать покупку кирпича и стеновых блоков максимально удобной и выгодной. Здесь вы можете найти объективную информацию о производителях строительных материалов, полу...
Visit a-brick.ruWe analyzed A-brick.ru page load time and found that the first response time was 574 ms and then it took 259.1 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.
a-brick.ru performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value9.2 s
1/100
25%
Value14.1 s
1/100
10%
Value380 ms
70/100
30%
Value0
100/100
15%
Value12.5 s
14/100
10%
574 ms
5634 ms
287 ms
293 ms
294 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 87% of them (67 requests) were addressed to the original A-brick.ru, 3% (2 requests) were made to Counter.rambler.ru and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain A-brick.ru.
Page size can be reduced by 2.0 MB (61%)
3.3 MB
1.3 MB
In fact, the total size of A-brick.ru main page is 3.3 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. 40% of websites need less resources to load. HTML takes 1.7 MB which makes up the majority of the site volume.
Potential reduce by 1.5 MB
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 331.1 kB, which is 20% 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 1.5 MB or 91% of the original size.
Potential reduce by 175.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. Obviously, A Brick needs image optimization as it can save up to 175.4 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 281.8 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 281.8 kB or 68% of the original size.
Potential reduce by 36.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. A-brick.ru needs all CSS files to be minified and compressed as it can save up to 36.3 kB or 78% of the original size.
Number of requests can be reduced by 28 (47%)
59
31
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A Brick. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
a-brick.ru
574 ms
www.a-brick.ru
5634 ms
widget.css
287 ms
widget.css
293 ms
main.css
294 ms
index_page.css
298 ms
ideaBlock.css
299 ms
style_site.css
437 ms
jquery.autocomplete.css
438 ms
colorCaptcha.css
443 ms
jquery.coolfieldset.css
445 ms
jquery.min.js
863 ms
jquery.bgiframe.js
582 ms
jquery.ajaxqueue.js
583 ms
jquery.autocomplete.js
590 ms
widget.js
593 ms
widget.js
727 ms
main.js
729 ms
blockFirstPage.js
737 ms
ideaBlock.js
742 ms
widget.js
871 ms
jquery.coolfieldset.min.js
875 ms
settings_page.css
597 ms
def_window_dialog.css
601 ms
myStyleDialog.css
714 ms
menu.css
728 ms
settings_form.css
730 ms
h_bg_img_left.png
150 ms
h_bg_img_right.png
144 ms
h_bg_img.jpg
439 ms
idea_img.png
147 ms
bg_menu_sub.png
150 ms
row_search.png
147 ms
thumb.png
295 ms
compare_ico.png
148 ms
basket_ico.png
150 ms
white_65_bg.png
267 ms
thumb.png
571 ms
thumb.png
582 ms
thumb.png
597 ms
thumb.png
592 ms
thumb.png
985 ms
thumb.png
585 ms
thumb.png
856 ms
thumb.png
872 ms
thumb.png
876 ms
thumb.png
887 ms
thumb.png
1043 ms
thumb.png
1022 ms
thumb.png
1045 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
229 ms
top100.jcn
499 ms
jquery-ui.min.js
1055 ms
thumb.png
0 ms
thumb.png
0 ms
thumb.png
0 ms
thumb.png
0 ms
thumb.png
0 ms
thumb.png
0 ms
twiter_ico.png
0 ms
google_ico.png
0 ms
watch.js
169 ms
ga.js
24 ms
hit
271 ms
__utm.gif
25 ms
hit
129 ms
top100.scn
130 ms
row_left_img.png
0 ms
cabinet_ico.png
0 ms
settings_ico.png
0 ms
gr_open_ico.png
0 ms
expanded.gif
0 ms
ugl_hint_panel.png
0 ms
nM2VqQ8UGm
167 ms
widget_ru_RU.js
188 ms
close_dialog.png
566 ms
bg_sreen_dialog.png
567 ms
a-brick.ru 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
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.
a-brick.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
a-brick.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A-brick.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), while the claimed language is English. Our system also found out that A-brick.ru 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.
a-brick.ru
Open Graph description is not detected on the main page of A Brick. 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: