5.4 sec in total
81 ms
4.9 sec
413 ms
Welcome to ecodes.biz homepage info - get ready to check Ecodes best content for United States right away, or after learning these important things about ecodes.biz
ICC Store
Visit ecodes.bizWe analyzed Ecodes.biz page load time and found that the first response time was 81 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ecodes.biz performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value12.2 s
0/100
25%
Value11.3 s
5/100
10%
Value2,010 ms
7/100
30%
Value1.028
2/100
15%
Value19.4 s
2/100
10%
81 ms
2947 ms
25 ms
54 ms
79 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ecodes.biz, 47% (34 requests) were made to Shop.iccsafe.org and 8% (6 requests) were made to Um.simpli.fi. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Shop.iccsafe.org.
Page size can be reduced by 1.8 MB (62%)
2.9 MB
1.1 MB
In fact, the total size of Ecodes.biz main page is 2.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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 78.0 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 18.6 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 78.0 kB or 83% of the original size.
Potential reduce by 99.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, Ecodes needs image optimization as it can save up to 99.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.2 MB
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 1.2 MB or 79% of the original size.
Potential reduce by 398.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. Ecodes.biz needs all CSS files to be minified and compressed as it can save up to 398.8 kB or 86% of the original size.
Number of requests can be reduced by 24 (41%)
58
34
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecodes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ecodes.biz
81 ms
shop.iccsafe.org
2947 ms
css
25 ms
c858f3458b08946d8702c74c652ab85e.css
54 ms
52e4a2136aa6984ac82fbe292edae5f0.css
79 ms
927938723e0252b7f377fe11e6b4f29c.css
112 ms
68e87547e2567fbebaf57d3519a17458.js
211 ms
763350eb99acaa2dc98cabb2ff082848.js
50 ms
satelliteLib-c2dd27504f62acc28c678e377f2293bafdcf12fb.js
7 ms
conversion.js
18 ms
bg.png
316 ms
ga.js
51 ms
menu-arrow.png
64 ms
logo.png
64 ms
block-cart-icon.png
65 ms
header-1v_p.jpg
138 ms
International_p.jpg
129 ms
engineering_p.jpg
131 ms
fire_codes_p.jpg
128 ms
energy_p.jpg
252 ms
water_p.jpg
276 ms
electrical_p.jpg
254 ms
California_p.jpg
259 ms
Accessibility_p.jpg
302 ms
training_and_certification_p.jpg
323 ms
sprite.png
327 ms
7036s14_1.jpg
307 ms
9542s15_3.jpg
321 ms
9626s15.jpg
373 ms
1108s9.jpg
378 ms
9509s13.jpg
370 ms
7103s15_1.jpg
394 ms
9024s15.jpg
373 ms
3810s15_1.jpg
419 ms
7028s14_1.jpg
442 ms
footer-logo.png
428 ms
oeEVQYYBjVpg-nn8NItjTw.ttf
49 ms
ZLqKeelYbATG60EpZBSDy6CWcynf_cDxXwCLxiixG1c.ttf
123 ms
0eC6fl06luXEYWpBSJvXCKCWcynf_cDxXwCLxiixG1c.ttf
85 ms
77FXFjRbGzN4aCrSFhlh3qCWcynf_cDxXwCLxiixG1c.ttf
85 ms
fontawesome-webfont.woff
472 ms
__utm.gif
25 ms
css-sprite.png
393 ms
53244.js
195 ms
satellite-56388a3164746d3f83002129.html
13 ms
s-code-contents-1440d2dd9a5625c323fe02bc1b053c1358ea7ad1.js
11 ms
phplive_v2.js.php
154 ms
dpx.js
144 ms
f.js
106 ms
148 ms
status.php
35 ms
p
7 ms
footprints.php
69 ms
dpx
6 ms
match_redirect
13 ms
34 ms
29931
15 ms
s71700785285793
39 ms
match_redirect
3 ms
tpid=CD29559EEAC4D456C619223702F49E7C
6 ms
lr
3 ms
lr.gif
4 ms
match_redirect
3 ms
sync
6 ms
match_redirect
8 ms
CD29559EEAC4D456C619223702F49E7C
39 ms
icon_online.png
30 ms
match_redirect
3 ms
ProfilesEngineServlet
19 ms
970728fa99b055fecbdc4a4651b1329a.css
49 ms
ProfilesEngineServlet
23 ms
tap.php
7 ms
pd.js
4 ms
ecodes.biz 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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>).
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.
ecodes.biz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ecodes.biz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecodes.biz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ecodes.biz 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.
ecodes.biz
Open Graph description is not detected on the main page of Ecodes. 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: