4.5 sec in total
442 ms
3.8 sec
242 ms
Click here to check amazing CONTAINEX content for Bulgaria. Otherwise, check out these important facts you probably never knew about containex.bg
CONTAINEX предлага контейнери & мобилни пространствени решения ✓ отговарят на 100% на индивидуалните потребности ✓ В цяла Европа ✓ Наемане или закупуване ► Изискайте оферта сега!
Visit containex.bgWe analyzed Containex.bg page load time and found that the first response time was 442 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
containex.bg performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value11.0 s
0/100
25%
Value14.3 s
1/100
10%
Value1,120 ms
23/100
30%
Value0
100/100
15%
Value12.1 s
16/100
10%
442 ms
475 ms
240 ms
601 ms
9 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 48% of them (23 requests) were addressed to the original Containex.bg, 23% (11 requests) were made to Static.containex.bg and 8% (4 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Containex.bg.
Page size can be reduced by 918.8 kB (48%)
1.9 MB
991.6 kB
In fact, the total size of Containex.bg main page is 1.9 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. 50% of websites need less resources to load. Javascripts take 894.8 kB which makes up the majority of the site volume.
Potential reduce by 73.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 32.9 kB, which is 38% 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 73.5 kB or 85% of the original size.
Potential reduce by 28.0 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. CONTAINEX images are well optimized though.
Potential reduce by 611.4 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 611.4 kB or 68% of the original size.
Potential reduce by 205.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. Containex.bg needs all CSS files to be minified and compressed as it can save up to 205.8 kB or 86% of the original size.
Number of requests can be reduced by 18 (41%)
44
26
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CONTAINEX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
containex.bg
442 ms
bg
475 ms
dtagent622_n_1019.js
240 ms
combined.css
601 ms
jquery.min.js
9 ms
js
31 ms
jwplayer.js
530 ms
combined.js
871 ms
jquery.scrollTo.min.js
394 ms
advertising.js
243 ms
containex-header-logo.ashx
438 ms
contactToggle.png
184 ms
containex-header-logo-small.ashx
276 ms
containex-dropdown-sale.ashx
437 ms
containex-sale-page-peel.ashx
267 ms
containex-icon-callback.ashx
265 ms
ctx-produktemodule-01.ashx
530 ms
containex-slide-containeranlagen.ashx
1051 ms
containex-slide-mietcontainer.ashx
878 ms
containex-slide-referenzprojekte.ashx
906 ms
containex-slide-sonderangebote.ashx
877 ms
walter-group-top_btn.ashx
494 ms
containex-greentechnology.ashx
635 ms
containex-raumsofort.ashx
814 ms
youtube.ashx
764 ms
facebook.ashx
895 ms
google-plus.ashx
947 ms
linkedin.ashx
999 ms
gtm.js
25 ms
no-repeat-s931006be05.png
202 ms
flags.png
740 ms
benefitsBG.png
249 ms
blueArrowRight.png
254 ms
blueCheckIcon.png
299 ms
containex-hintergrund-left.ashx
1230 ms
containex-hintergrund-right.ashx
1247 ms
analytics.js
7 ms
conversion_async.js
19 ms
linkid.js
6 ms
collect
5 ms
collect
70 ms
54 ms
30 ms
ga-audiences
19 ms
common.js
51 ms
util.js
52 ms
marker.js
51 ms
print.css
127 ms
containex.bg 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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
containex.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
containex.bg 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
Tap targets are not sized appropriately
BG
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Containex.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian 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 Containex.bg 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.
containex.bg
Open Graph description is not detected on the main page of CONTAINEX. 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: