30 sec in total
1.1 sec
28.1 sec
901 ms
Visit 304industrialpark.com now to see the best up-to-date 304 Industrial Park content and also check out these interesting facts you probably never knew about 304industrialpark.com
304 Industrial Park is Thailand's business developer of industrial district. Our industrial parks are ideally positioned within the industry cluster areas
Visit 304industrialpark.comWe analyzed 304industrialpark.com page load time and found that the first response time was 1.1 sec and then it took 29 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
304industrialpark.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value9.9 s
0/100
25%
Value22.0 s
0/100
10%
Value720 ms
41/100
30%
Value1.173
1/100
15%
Value18.8 s
3/100
10%
1088 ms
560 ms
554 ms
545 ms
565 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 72% of them (115 requests) were addressed to the original 304industrialpark.com, 9% (15 requests) were made to Google.com and 9% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (12.3 sec) belongs to the original domain 304industrialpark.com.
Page size can be reduced by 1.2 MB (12%)
9.5 MB
8.3 MB
In fact, the total size of 304industrialpark.com main page is 9.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 7.9 MB which makes up the majority of the site volume.
Potential reduce by 69.3 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 26.1 kB, which is 32% 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 69.3 kB or 86% of the original size.
Potential reduce by 12.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. 304 Industrial Park images are well optimized though.
Potential reduce by 805.1 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 805.1 kB or 70% of the original size.
Potential reduce by 273.7 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. 304industrialpark.com needs all CSS files to be minified and compressed as it can save up to 273.7 kB or 86% of the original size.
Number of requests can be reduced by 35 (23%)
153
118
The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 304 Industrial Park. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
304industrialpark.com
1088 ms
304.css
560 ms
responsive.css
554 ms
font-awesome.css
545 ms
styles.css
565 ms
bootstrap.css
859 ms
function.js
553 ms
jquery.min.js
1987 ms
bootstrap.min.js
1120 ms
jquery-1.11.1.min.js
1713 ms
animate.css
1231 ms
304IP-jquery-function.js
1237 ms
popup.css
1561 ms
popup.js
1762 ms
slider-pro.min.css
1910 ms
jquery.sliderPro.min.js
2550 ms
owl.theme.css
2238 ms
owl.carousel.js
2301 ms
owl.carousel.css
2936 ms
owl.transitions.css
2515 ms
viewportchecker.js
2629 ms
analytics.js
74 ms
close.png
775 ms
icon-tel.png
927 ms
icon-tel-2.png
1534 ms
icon-marketing.png
1219 ms
icon-fax.png
1198 ms
icon-hr.png
1402 ms
flag-en.jpg
1915 ms
flag-th.jpg
1636 ms
flag_china.jpg
1747 ms
flag-jp.jpg
1745 ms
verify_image.php
2028 ms
logo-304IP.png
2050 ms
1.jpg
6018 ms
2.jpg
4959 ms
3.jpg
8467 ms
4.jpg
4984 ms
5.jpg
12325 ms
1.jpg
6119 ms
2.jpg
7083 ms
3.jpg
8235 ms
4.jpg
7563 ms
5.jpg
9658 ms
icon-bg-red.png
7599 ms
icon-bg-blue.png
8077 ms
icon-02-red.png
8127 ms
icon-02-blue.png
8594 ms
icon-03-red.png
8668 ms
icon-03-blue.png
8765 ms
why-01.png
8994 ms
embed
259 ms
embed
411 ms
why-02.png
9134 ms
collect
12 ms
HelveticaNeueLTStd-BdCn.otf
9243 ms
js
48 ms
init_embed.js
34 ms
fontawesome-webfont.woff
9599 ms
why-05.png
9076 ms
why-06.png
9166 ms
why-07.png
9405 ms
common.js
58 ms
map.js
58 ms
google4.png
21 ms
overlay.js
14 ms
util.js
14 ms
onion.js
12 ms
search_impl.js
13 ms
i-01-red.png
9318 ms
openhand_8_8.cur
65 ms
ViewportInfoService.GetViewportInfo
97 ms
controls.js
7 ms
ViewportInfoService.GetViewportInfo
23 ms
transparent.png
21 ms
kh
136 ms
css
109 ms
entity11.png
25 ms
mapcnt6.png
90 ms
sv9.png
106 ms
tmapctrl.png
100 ms
i-01-bule.png
9260 ms
i-02-red.png
9296 ms
vt
60 ms
vt
80 ms
vt
80 ms
vt
88 ms
vt
80 ms
vt
80 ms
vt
88 ms
vt
111 ms
vt
117 ms
vt
108 ms
vt
114 ms
vt
123 ms
vt
133 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
31 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
34 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
49 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
48 ms
AuthenticationService.Authenticate
17 ms
i-02-bule.png
9235 ms
i-03-red.png
9356 ms
i-03-bule.png
9219 ms
i-04-red.png
9183 ms
i-04-bule.png
9126 ms
i-05-red.png
9207 ms
i-05-bule.png
9342 ms
banner-01.jpg
12068 ms
banner-01-mobile.jpg
10862 ms
thailand-board.jpg
9245 ms
dubbleA.jpg
6526 ms
hgsr.jpg
6663 ms
stats.js
2 ms
AuthenticationService.Authenticate
13 ms
emerson.jpg
5835 ms
cmk.jpg
5986 ms
QuotaService.RecordEvent
14 ms
BLC.jpg
5091 ms
canon.jpg
4857 ms
scg.jpg
5098 ms
aisin-logo.jpg
4687 ms
toshiba.jpg
4791 ms
kolto.jpg
4718 ms
pri.jpg
4778 ms
tawa-logo.jpg
5173 ms
logo.jpg
4834 ms
2.jpg
4736 ms
3.jpg
4633 ms
4.jpg
4808 ms
5.jpg
4680 ms
6.jpg
4584 ms
7.jpg
4517 ms
8.jpg
4599 ms
9.jpg
4597 ms
10.jpg
4500 ms
11.jpg
4606 ms
12.jpg
4519 ms
13.jpg
4478 ms
14.jpg
4392 ms
20170821124203.jpg
7438 ms
20170821124423.jpg
7945 ms
20170718173855.jpg
5337 ms
20170718174926.jpg
7917 ms
20170707132315.jpg
7076 ms
20170630154614.jpg
7147 ms
20170524135822.jpg
6374 ms
20170201114914.jpg
8521 ms
20161110153744.jpg
10421 ms
icon-form.png
6704 ms
bg-icon.png
6933 ms
bg-about.jpg
9055 ms
bg-investment.jpg
9957 ms
bg-why304ip.jpg
8740 ms
bullet-red.png
6849 ms
bg-304park.jpg
8122 ms
bg-link.jpg
11527 ms
bg-news.jpg
9447 ms
icon-plus.jpg
8739 ms
icon-munit.jpg
516 ms
304industrialpark.com 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
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.
304industrialpark.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
304industrialpark.com 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 304industrialpark.com 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 304industrialpark.com 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.
304industrialpark.com
Open Graph description is not detected on the main page of 304 Industrial Park. 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: