6.2 sec in total
721 ms
5.2 sec
256 ms
Click here to check amazing Kamax content for Bulgaria. Otherwise, check out these important facts you probably never knew about kamax.bg
Фабрика за щори и сенници КАМАКС произвежда и монтира пълна гама вътрешни и външни щори, сенници, тенти, мрежи против насекоми и сгъваеми врати хармоника.
Visit kamax.bgWe analyzed Kamax.bg page load time and found that the first response time was 721 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kamax.bg performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value12.2 s
0/100
25%
Value7.9 s
23/100
10%
Value280 ms
80/100
30%
Value0.025
100/100
15%
Value8.5 s
38/100
10%
721 ms
1544 ms
26 ms
941 ms
1154 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 44% of them (44 requests) were addressed to the original Kamax.bg, 10% (10 requests) were made to Static.xx.fbcdn.net and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Kamax.bg.
Page size can be reduced by 340.7 kB (21%)
1.6 MB
1.3 MB
In fact, the total size of Kamax.bg main page is 1.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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 34.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 8.4 kB, which is 19% 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 34.7 kB or 77% of the original size.
Potential reduce by 30.8 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. Kamax images are well optimized though.
Potential reduce by 207.9 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 207.9 kB or 55% of the original size.
Potential reduce by 67.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. Kamax.bg needs all CSS files to be minified and compressed as it can save up to 67.3 kB or 84% of the original size.
Number of requests can be reduced by 50 (54%)
92
42
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kamax. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
kamax.bg
721 ms
www.kamax.bg
1544 ms
css
26 ms
kamax2012.css
941 ms
jquery.min.js
1154 ms
jquery.nicescroll.min.js
999 ms
style2.css
641 ms
modernizr.custom.28468.js
524 ms
jquery.cslider.js
503 ms
lightbox.css
672 ms
jquery.als-1.7.js
1348 ms
lightbox.js
968 ms
element.js
33 ms
bgr.jpg
740 ms
close.png
193 ms
loading.gif
191 ms
prev.png
192 ms
next.png
191 ms
dict_logo_68_1392988229.png
409 ms
flag-en.gif
340 ms
16_1455120288_pic.jpg
1320 ms
9_1438679812_pic.jpg
1139 ms
1_1438679257_pic.jpg
1349 ms
10_1392451462_pic.jpg
1199 ms
7_1392449971_pic.jpg
1395 ms
124_1456817350_logo.jpg
923 ms
a1.jpg
1105 ms
a1-h.jpg
1442 ms
a2.jpg
1300 ms
a2-h.jpg
1357 ms
a3.jpg
1460 ms
a3-h.jpg
1473 ms
pic_7.jpg
1603 ms
pic_8.jpg
1566 ms
pic_6.jpg
1593 ms
pic_9.jpg
1620 ms
pic_8.jpg
1623 ms
all.js
20 ms
bgr-logo.png
1624 ms
bullet-topmenu.gif
1717 ms
translateelement.css
84 ms
main.js
118 ms
DXI1ORHCpsQm3Vp6mXoaTWeP1y_Bkidl4ESyB_O2G_c.ttf
39 ms
K88pR3goAWT7BTt32Z01m6CWcynf_cDxXwCLxiixG1c.ttf
40 ms
MTP_ySUJH_bn48VBG8sNSmeP1y_Bkidl4ESyB_O2G_c.ttf
48 ms
k3k702ZOKiLJc3WVjuplzGeP1y_Bkidl4ESyB_O2G_c.ttf
40 ms
EInbV5DfGHOiMmvb1Xr-hmeP1y_Bkidl4ESyB_O2G_c.ttf
47 ms
211 ms
xd_arbiter.php
21 ms
xd_arbiter.php
64 ms
plusone.js
76 ms
main-menu.png
1660 ms
search-icon.png
1664 ms
bullet-try.png
1693 ms
arrows.png
1673 ms
shadow.png
1670 ms
widgets.js
133 ms
bullet-topmenu2.gif
1749 ms
icon_top.png
1823 ms
ga.js
9 ms
element_main.js
42 ms
likebox.php
463 ms
__utm.gif
80 ms
c
334 ms
cb=gapi.loaded_0
79 ms
cb=gapi.loaded_1
100 ms
fastbutton
163 ms
piwik.js
692 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
129 ms
postmessageRelay
42 ms
3193398744-postmessagerelay.js
38 ms
rpc:shindig_random.js
35 ms
cb=gapi.loaded_0
19 ms
cb=gapi.loaded_1
27 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
34 ms
cb=gapi.loaded_0
9 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.bg.html
43 ms
kyEKgjk51ZE.css
56 ms
xgj7bXhJNEH.css
50 ms
jot
192 ms
q68gy-v_YMF.js
57 ms
FJmpeSpHpjS.js
57 ms
0wM5s1Khldu.js
55 ms
1bNoFZUdlYZ.js
52 ms
548490_338754546190115_1306081262_n.jpg
109 ms
1621967_644652915600275_1772277983_n.jpg
77 ms
11887990_1029395837093734_5206547141274275933_n.jpg
78 ms
12311128_926103820804857_6697944846152017119_n.jpg
81 ms
10389232_795781677137487_3021070848069394264_n.jpg
82 ms
12814482_984841731571103_5406840501178338618_n.jpg
82 ms
11043259_1409000689411699_8964555568788540193_n.jpg
81 ms
wL6VQj7Ab77.png
22 ms
s7jcwEQH7Sx.png
23 ms
translate_24dp.png
48 ms
l
49 ms
cleardot.gif
76 ms
I6-MnjEovm5.js
31 ms
pQrUxxo5oQp.js
32 ms
te_ctrl3.gif
11 ms
piwik.php
338 ms
kamax.bg accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
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>).
kamax.bg 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
Missing source maps for large first-party JavaScript
kamax.bg SEO score
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
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kamax.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Kamax.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.
kamax.bg
Open Graph description is not detected on the main page of Kamax. 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: