6.4 sec in total
965 ms
5 sec
473 ms
Welcome to carbon.ee homepage info - get ready to check Carbon best content right away, or after learning these important things about carbon.ee
Visit carbon.eeWe analyzed Carbon.ee page load time and found that the first response time was 965 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
carbon.ee performance score
name
value
score
weighting
Value1.7 s
91/100
10%
Value2.0 s
97/100
25%
Value3.2 s
92/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.7 s
100/100
10%
965 ms
24 ms
842 ms
32 ms
53 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 77% of them (43 requests) were addressed to the original Carbon.ee, 4% (2 requests) were made to Ajax.googleapis.com and 4% (2 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Carbon.ee.
Page size can be reduced by 585.6 kB (17%)
3.5 MB
2.9 MB
In fact, the total size of Carbon.ee main page is 3.5 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. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 90.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 90.5 kB or 80% of the original size.
Potential reduce by 85.2 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. Carbon images are well optimized though.
Potential reduce by 227.6 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 227.6 kB or 67% of the original size.
Potential reduce by 182.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. Carbon.ee needs all CSS files to be minified and compressed as it can save up to 182.3 kB or 90% of the original size.
Number of requests can be reduced by 19 (35%)
54
35
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carbon. 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.
www.carbon.ee
965 ms
css
24 ms
all-2922.css
842 ms
jquery.min.js
32 ms
jquery-ui.min.js
53 ms
all-2922.js
1065 ms
pinit.js
7 ms
back_pattern.png
165 ms
Carbon%20fiber%20CNC%20cut%20detail%20%20Erismet-large22.png
739 ms
logo%20sloganiga.png
259 ms
et.png
220 ms
en.png
228 ms
Kuulutusse.png
355 ms
3mm%20500x650.png
356 ms
1mm%20500x650.png
438 ms
1mma4.jpg
448 ms
5mm%20500x650.png
372 ms
2mm%20500x650.png
596 ms
4mm%20500x650.png
588 ms
Carbon%20fiber%20spreaded%20carbon.ee%20erismet%203K%20twill%20fabric.JPG
492 ms
5mm%20A4.jpg
651 ms
6mm%20500x650.png
670 ms
3mmA5.JPG
611 ms
carbon-fibre-650twill-carbon-ee.jpg
820 ms
6mm%20A5.JPG
710 ms
2mma4.jpg
721 ms
4mm%20A5.JPG
753 ms
6mm%20A4.jpg
774 ms
5mm%20A5.JPG
824 ms
3mma4.jpg
836 ms
img_paypal.png
843 ms
logo-epl.png
860 ms
all.js
291 ms
cart.png
881 ms
arrow-down.png
923 ms
button-search.png
936 ms
camera_skins.png
896 ms
camera-loader.gif
907 ms
Carbon%20fiber%20Fibre%20Sheet%20Plate%20Estonia%20Europe.JPG
1683 ms
carousel-buttons.png
939 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
88 ms
subtlenet2.png
899 ms
location.png
914 ms
phone.png
919 ms
email.png
935 ms
plusone.js
67 ms
border.png
1055 ms
pinit_main.js
23 ms
controls.png
992 ms
top.png
966 ms
cb=gapi.loaded_0
6 ms
126 ms
xd_arbiter.php
224 ms
xd_arbiter.php
428 ms
ping
57 ms
Carbon.ee%20erismet%20estonia%20twill%20weave%203K%2012K%20glossy%20carbon%20fiber%20sheet%20plate%20panel.JPG
874 ms
carbon.ee 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
Links do not have a discernible name
carbon.ee 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
carbon.ee SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carbon.ee 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 Carbon.ee 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.
carbon.ee
Open Graph description is not detected on the main page of Carbon. 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: