38.2 sec in total
765 ms
37 sec
495 ms
Click here to check amazing Pg content for Thailand. Otherwise, check out these important facts you probably never knew about pg.co.th
Visit pg.co.thWe analyzed Pg.co.th page load time and found that the first response time was 765 ms and then it took 37.4 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.
pg.co.th performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value9.5 s
0/100
25%
Value29.6 s
0/100
10%
Value1,610 ms
12/100
30%
Value0.005
100/100
15%
Value31.2 s
0/100
10%
765 ms
3284 ms
752 ms
754 ms
1534 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 98% of them (95 requests) were addressed to the original Pg.co.th, 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Pg.co.th.
Page size can be reduced by 303.1 kB (5%)
5.6 MB
5.3 MB
In fact, the total size of Pg.co.th main page is 5.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. 50% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 104.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 104.5 kB or 81% of the original size.
Potential reduce by 103.4 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. Pg images are well optimized though.
Potential reduce by 29.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 65.6 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. Pg.co.th needs all CSS files to be minified and compressed as it can save up to 65.6 kB or 23% of the original size.
Number of requests can be reduced by 51 (59%)
86
35
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
pg.co.th
765 ms
www.pg.co.th
3284 ms
select2.min.css
752 ms
iconfonts.css
754 ms
frontend.min.css
1534 ms
tooltip.css
762 ms
tooltipster-sideTip-shadow.min.css
794 ms
featherlight.css
995 ms
css
32 ms
lity.min.css
1513 ms
style.min.css
1769 ms
all-css.min.css
1822 ms
asl_responsive.css
1553 ms
styles.css
1742 ms
frontend.css
2259 ms
rs6.css
2318 ms
style.css
2309 ms
base.css
2500 ms
layout.css
3054 ms
shortcodes.css
2836 ms
animations.min.css
3047 ms
jquery.ui.all.css
3099 ms
jplayer.blue.monday.css
3115 ms
responsive.css
3559 ms
jquery.min.js
3995 ms
jquery-migrate.min.js
3796 ms
frontend.js
4211 ms
events.js
3872 ms
jquery.fitvids.min.js
3888 ms
frontend.min.js
4450 ms
revolution.tools.min.js
5476 ms
rs6.min.js
5513 ms
css
15 ms
core.min.js
4529 ms
datepicker.min.js
4597 ms
jquery.typewatch.js
4739 ms
featherlight.js
4967 ms
select2.full.min.js
5591 ms
tooltip.js
5405 ms
lity.min.js
5539 ms
colorbrightness.min.js
5216 ms
owl.carousel.min.js
5750 ms
index.js
5555 ms
index.js
5630 ms
mouse.min.js
5584 ms
sortable.min.js
5085 ms
tabs.min.js
5207 ms
accordion.min.js
5510 ms
plugins.js
6286 ms
menu.js
5479 ms
animations.min.js
5520 ms
jplayer.min.js
5346 ms
translate3d.js
5235 ms
jquery.flexslider-min.js
5544 ms
scripts.js
5762 ms
357x39.png
2884 ms
slide-1.png
12485 ms
%E0%B9%83%E0%B8%AA%E0%B9%88-slide-1-1980x838-1.png
10168 ms
%E0%B9%83%E0%B8%AA%E0%B9%88-slide-_3_1980x838.png
13790 ms
%E0%B9%83%E0%B8%AA%E0%B9%88-slide-4_1980x838.png
12269 ms
380x441-TEXTILE-1.jpg
4773 ms
380x441-GARMENT-1.jpg
4810 ms
380x441-UNIFORM-2.jpg
6516 ms
380x441-SPORTWEAR-1.jpg
6813 ms
380x441-INNERWEAR-1.jpg
8009 ms
380x441-HEALTHCARE-1.jpg
8823 ms
other-pro_380x441-1.jpg
9346 ms
banner-custom-1.png
17401 ms
banner-custom-2.png
14358 ms
banner-custom-3.png
16255 ms
REDUCE-CARBON-EMISSION-banner.png
15051 ms
REDUCE-CARBON-EMISSION-icon.png
15019 ms
RECYCLING-MATERIALS-banner.png
16331 ms
AvenirLT35Light.woff
15299 ms
AvenirLTLight.woff
15794 ms
AvenirLTRoman.woff
15750 ms
FontsFreeNetAvenirLTStdHeavy.woff
15990 ms
AvenirLTBook.woff
16273 ms
FontsFreeNetAvenirLTStdBlack.woff
16180 ms
RobotoBlack.woff
17122 ms
RobotoRegular.woff
16919 ms
mfn-icons.woff
17223 ms
1.aw-homepage-News-11-25-63_03.png
18388 ms
WASTE-WATER-TREATMENT-banner.png
18566 ms
WASTE-WATER-TREATMENT-icon.png
18342 ms
SOLAR-ENERGY-banner.png
19289 ms
SOLAR-ENERGY-icon.png
18683 ms
357x39-G-300x33.png
17533 ms
line-icon.png
19771 ms
facbook-icon.png
19352 ms
th.png
17923 ms
us.png
17936 ms
arrow-right.png
18719 ms
nav-prev.png
18633 ms
nav-next.png
17083 ms
top_bar_right_shadow.png
15044 ms
icon-search.png
16730 ms
pg.co.th 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
pg.co.th best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
pg.co.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pg.co.th 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 Pg.co.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.
pg.co.th
Open Graph description is not detected on the main page of Pg. 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: