5.4 sec in total
1 sec
4.2 sec
220 ms
Visit fubag.ru now to see the best up-to-date FUBAG content for Russia and also check out these interesting facts you probably never knew about fubag.ru
Официальный интернет-магазин Фубаг - строительное оборудование и инструменты Fubag: сварочное оборудование, компрессоры, бензотехника, теплогенераторы, ПЗУ, камнерезные станки и алмазные диски с доста...
Visit fubag.ruWe analyzed Fubag.ru page load time and found that the first response time was 1 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fubag.ru performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value13.4 s
0/100
25%
Value12.3 s
3/100
10%
Value1,140 ms
22/100
30%
Value0.076
95/100
15%
Value18.1 s
3/100
10%
1023 ms
34 ms
800 ms
226 ms
1219 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 78% of them (62 requests) were addressed to the original Fubag.ru, 9% (7 requests) were made to Api-maps.yandex.ru and 4% (3 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Fubag.ru.
Page size can be reduced by 567.7 kB (26%)
2.2 MB
1.6 MB
In fact, the total size of Fubag.ru main page is 2.2 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. 30% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 174.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. This page needs HTML code to be minified as it can gain 33.5 kB, which is 13% 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 174.5 kB or 70% of the original size.
Potential reduce by 253.6 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, FUBAG needs image optimization as it can save up to 253.6 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 29.5 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 29.5 kB or 41% of the original size.
Potential reduce by 110.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. Fubag.ru needs all CSS files to be minified and compressed as it can save up to 110.1 kB or 84% of the original size.
Number of requests can be reduced by 13 (18%)
72
59
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUBAG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
fubag.ru
1023 ms
jquery.min.js
34 ms
template_d2c726252e301de5cf5beaff07268996.css
800 ms
226 ms
template_3eb7d274b1bbd3f2b5cc26ae44611517.js
1219 ms
634 ms
combine.xml
582 ms
ba.js
213 ms
code.js
425 ms
preloader.gif
414 ms
logo_fub_rgb.png
168 ms
lang_bg.png
145 ms
menu.png
700 ms
menu_arrows.png
407 ms
hr2.png
406 ms
15862fa9d44613423eb116671a933e9a.png
408 ms
e0b7b349db1fb4f51cc9e0c9ba09a0fc.png
410 ms
bd3138dd8d8b6e68f326763a39e77dcf.png
414 ms
e79564b1e2b7625738deaddef75c619b.png
425 ms
e91c4e32238d5033e3a7f72403bf7fe2.png
705 ms
afc725ed0d6c2b8adcdc9d49206e1022.png
425 ms
8233e21060e06cf019062b0afa1a556f.png
436 ms
7ac1a031c3d90acd5fc3755c7b65717b.png
532 ms
f5bfe738ee41e0cbf54273dae14f8ec9.png
568 ms
7b0d4971b3c23eefa95e36e88f20d1b2.png
837 ms
ae3a5df4df4d21b56944e8d32b46b82e.png
572 ms
dcfe52c030a5db4373c0820812f37830.png
664 ms
076327701387bdb5d5f7e7a46a3ee078.png
702 ms
884f907d554c672e8fa2ae485ece01db.png
706 ms
f3e31168f95abfebe829812592f702a5.png
965 ms
0ab447046510b89c24c6a059d9b95a28.png
828 ms
dd63f1ef50efd32d6d24a74292f82f32.png
834 ms
e0319f9b612fd22f005d7cb35351057b.png
834 ms
4bfad0cc4764f1a4f53b65226956bcb8.png
841 ms
877b2106c360ed0f07e5a918f9dd9def.png
962 ms
06588874661e72e4f46f7e4543277387.png
965 ms
5e3955e31f3a77616039696b76b785f4.png
966 ms
ebbafee441d7c2ace19c5c0121845e25.png
967 ms
75473f2c666ca6a1a455804f119183e6.png
976 ms
f55276a6e8c881060692c2eb29b9bd16.png
1096 ms
a6357378b7928be9f0d8879e00574f6a.png
1138 ms
e8e1286afc6ea1da1e005e96a8e08056.png
1138 ms
84fab12727b2b1e20f91ced0e0bdc3de.png
1137 ms
a280181f20e6459926af49a957c52510.png
1136 ms
52eb99ed78ca40f11542506231d806bf.png
1133 ms
hit
388 ms
watch.js
39 ms
analytics.js
38 ms
collect
16 ms
154587de91e67a9d7c05a2eda3f11838.png
1090 ms
a895bd9d5283b63c5bb13d6b50c3122d.png
1114 ms
bx_stat
394 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
113 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
165 ms
4965b66fe115b2f2ed500ece66514d86.cur
276 ms
77492cf358d8b12629399322926c93f2.cur
386 ms
845e2d6a54140424e80229db4aac05f8.png
872 ms
d01ed2bd6cf3b53f0fbd92c48db7d0b6.png
874 ms
4d626243725c075e0196fc603ac861b1.png
873 ms
hit
130 ms
12b14718a1bc86e44974ae15c65c9ced.jpg
1264 ms
ec38f7163fa41d750e39f259a9845dab.jpg
1351 ms
counter
154 ms
275eb4c7849337a76faabe689b87a14e.jpg
1706 ms
f02d7bd9eade0df36ca20c5c42f8498b.jpg
1005 ms
separator_1.png
989 ms
fringe_large.png
978 ms
hr.png
1022 ms
47e1a09ddfc127d2fcc74a6c90d2dcb8.jpeg
1120 ms
corners.png
1000 ms
3a5318f5b5e0a3daf1ef941af76458e1.jpg
1297 ms
px.gif
1009 ms
socials.png
1105 ms
anhor_menu_bg.png
1119 ms
home_icon.png
1138 ms
anhor_menu_points.png
1063 ms
fringe_very_small.png
1103 ms
slider_dots.png
1120 ms
tracker
153 ms
header_wrapper.png
133 ms
fubag.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
Buttons do not have an accessible name
Form elements do not have associated labels
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.
fubag.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fubag.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fubag.ru 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 Fubag.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.
fubag.ru
Open Graph description is not detected on the main page of FUBAG. 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: