16.2 sec in total
1.6 sec
14.1 sec
375 ms
Click here to check amazing Ecocenter Diw content for Thailand. Otherwise, check out these important facts you probably never knew about ecocenter.diw.go.th
เมืองอุตสาหกรรมต้นแบบ ประเทศไทย
Visit ecocenter.diw.go.thWe analyzed Ecocenter.diw.go.th page load time and found that the first response time was 1.6 sec and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ecocenter.diw.go.th performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value15.7 s
0/100
25%
Value24.3 s
0/100
10%
Value1,140 ms
22/100
30%
Value0.182
67/100
15%
Value14.8 s
8/100
10%
1645 ms
568 ms
1791 ms
602 ms
2112 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 77% of them (68 requests) were addressed to the original Ecocenter.diw.go.th, 10% (9 requests) were made to Google.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Ecocenter.diw.go.th.
Page size can be reduced by 798.7 kB (18%)
4.5 MB
3.7 MB
In fact, the total size of Ecocenter.diw.go.th main page is 4.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. 50% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 64.6 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 64.6 kB or 80% of the original size.
Potential reduce by 97.3 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. Ecocenter Diw images are well optimized though.
Potential reduce by 252.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 252.4 kB or 66% of the original size.
Potential reduce by 384.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. Ecocenter.diw.go.th needs all CSS files to be minified and compressed as it can save up to 384.3 kB or 85% of the original size.
Number of requests can be reduced by 49 (58%)
84
35
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecocenter Diw. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
1645 ms
jsystem.css
568 ms
bootstrap.css
1791 ms
superfish.css
602 ms
template.css
2112 ms
bootstrap_responsive.css
1187 ms
updates.css
1167 ms
custom.css
1493 ms
my_sitemap.css
1195 ms
my_hoverbox.css
1760 ms
my_vertical_tabs.css
1753 ms
my_latest_posts.css
1772 ms
my_newsletter-signup.css
2090 ms
my_search_panel.css
2328 ms
my_K2.css
2340 ms
my_linkdownload.css
2356 ms
responsive.css
2381 ms
css
23 ms
css
37 ms
style.css
2663 ms
style.css
2688 ms
jquery.min.js
3808 ms
jquery-noconflict.js
2934 ms
jquery-migrate.min.js
2924 ms
bootstrap.min.js
3278 ms
modernizr-2.6.2.js
3236 ms
plugins.js
3251 ms
superfish_menu.js
3510 ms
script.js
3525 ms
jquery.iosslider.min.js
4147 ms
jquery.iosslider.kalypso.js
3831 ms
challenge
68 ms
kallyas_script.js
3326 ms
prettyPhoto.css
3802 ms
jquery.prettyPhoto.js
3878 ms
stylesheet.css
2271 ms
ga.js
105 ms
logo-eco.png
384 ms
banner_oce_nwot4.jpg
2381 ms
banner2.jpg
2727 ms
banner3.jpg
2348 ms
banner4.jpg
3069 ms
1_5_20.jpg
1557 ms
2_5_20.jpg
1572 ms
3_5_20%E0%B8%AA%E0%B8%B4%E0%B9%88%E0%B8%87%E0%B9%81%E0%B8%A7%E0%B8%94%E0%B8%A5%E0%B9%89%E0%B8%AD%E0%B8%A1.jpg
2720 ms
4_5_20%E0%B8%AA%E0%B8%B1%E0%B8%87%E0%B8%84%E0%B8%A1.jpg
2478 ms
5_5_20%E0%B8%9A%E0%B8%A3%E0%B8%B4%E0%B8%AB%E0%B8%B2%E0%B8%A3%E0%B8%88%E0%B8%B1%E0%B8%94%E0%B8%81%E0%B8%B2%E0%B8%A3.jpg
3511 ms
570x0_9b514174bf_news-4.jpg
3851 ms
news4-brochure.jpg
5706 ms
template6.gif
3291 ms
iconFB30.png
3313 ms
iconTW30.png
3666 ms
570x0_9b514174bf_econews.jpg
5331 ms
570x0_9b514174bf_seminar_indicator.jpg
5406 ms
570x0_217c43079e_world06.jpg
5038 ms
570x0_217c43079e_world16.jpg
5677 ms
570x0_217c43079e_world07.jpg
5595 ms
bn_questionnaire.png
6176 ms
all.js
29 ms
recaptcha.js
6 ms
fdNPhfiab-XXWFZC4cs1ZwRW1YVuobzzx0F9p6k9YN8.js
78 ms
icon_search.png
5895 ms
glare-effect.png
5911 ms
loader_dark.gif
6101 ms
controls.png
6163 ms
DB%20Ozone%20X%20v3.2.woff
7034 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
122 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
133 ms
256 ms
__utm.gif
193 ms
refresh.png
41 ms
bgpattren.jpg
6845 ms
social-icons-sprite.png
6418 ms
arrow_totop.png
6554 ms
audio.png
155 ms
text.png
156 ms
help.png
157 ms
logo.png
164 ms
xd_arbiter.php
165 ms
xd_arbiter.php
177 ms
spark4.png
6419 ms
spark2.png
6470 ms
spark5.png
6843 ms
spark3.png
7004 ms
spark.png
7001 ms
spark6.png
7040 ms
reload
33 ms
dos_captcha.jpg
50 ms
ecocenter.diw.go.th accessibility score
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 input fields do not have accessible names
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
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ecocenter.diw.go.th 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
ecocenter.diw.go.th SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
TH
TH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecocenter.diw.go.th can be misinterpreted by Google and other search engines. Our service has detected that Thai is used on the page, and it matches the claimed language. Our system also found out that Ecocenter.diw.go.th 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.
ecocenter.diw.go.th
Open Graph description is not detected on the main page of Ecocenter Diw. 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: