8.4 sec in total
1.9 sec
5.8 sec
681 ms
Visit srt.co.th now to see the best up-to-date SRT content for Thailand and also check out these interesting facts you probably never knew about srt.co.th
ได้เปิดให้บริการมายาวนาน ได้นำเข้าสินค้าจากทั่วโลกมากมาย อาทิเช่น หัวแร้งบัดกรี Hakko (HAKKO 980,HAKKO 981) สินค้าจากญี่ปุ่น. คีม Piergiacomi สินค้าจากอิตาลี, ท่อหด Woer สินค้าจากจีน และยังมีสินค้าอีก...
Visit srt.co.thWe analyzed Srt.co.th page load time and found that the first response time was 1.9 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
srt.co.th performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value24.7 s
0/100
25%
Value24.5 s
0/100
10%
Value2,540 ms
4/100
30%
Value0.18
67/100
15%
Value41.1 s
0/100
10%
1861 ms
1048 ms
521 ms
1063 ms
801 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 65% of them (37 requests) were addressed to the original Srt.co.th, 18% (10 requests) were made to Static.xx.fbcdn.net and 9% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Srt.co.th.
Page size can be reduced by 173.5 kB (8%)
2.2 MB
2.1 MB
In fact, the total size of Srt.co.th main page is 2.2 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. 30% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 49.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 16.4 kB, which is 29% 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 49.3 kB or 88% of the original size.
Potential reduce by 52.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. SRT images are well optimized though.
Potential reduce by 20.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 20.4 kB or 65% of the original size.
Potential reduce by 51.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. Srt.co.th needs all CSS files to be minified and compressed as it can save up to 51.6 kB or 87% of the original size.
Number of requests can be reduced by 23 (43%)
54
31
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SRT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
srt.co.th
1861 ms
script.js
1048 ms
swfobject_modified.js
521 ms
default.css
1063 ms
portal.css
801 ms
style.css
1355 ms
swfobject.js
794 ms
flag.js
310 ms
get_flash_player.gif
65 ms
page_gl.png
310 ms
sheet_s.png
310 ms
sheet_h.png
262 ms
sheet_v.png
263 ms
nav.png
301 ms
menuitem.png
308 ms
spacer.gif
523 ms
subitem.png
523 ms
header.jpg
608 ms
New-icon2.gif
596 ms
%E0%B9%81%E0%B8%99%E0%B8%B0%E0%B8%99%E0%B8%B3%E0%B8%AA%E0%B8%B4%E0%B8%99%E0%B8%84%E0%B9%89%E0%B8%B2%E0%B9%83%E0%B8%AB%E0%B8%A1%E0%B9%88.png
614 ms
FR-400.jpg
1424 ms
FX-801.jpg
1575 ms
FU500,FU600.jpg
2345 ms
fr810_101.jpg
1671 ms
AutoParts.jpg
3030 ms
HG2310%20LCD.jpg
1154 ms
home_img_eyeCatch8.jpg
1737 ms
CAM3.png
3351 ms
vmenublock_s.png
1758 ms
vmenublock_h.png
1856 ms
vmenublock_v.png
1924 ms
vmenublockheader.png
2037 ms
vmenuitem.png
2119 ms
block_s.png
2187 ms
block_h.png
2296 ms
block_v.png
2380 ms
blockheader.png
2462 ms
blockcontentbullets.png
2526 ms
fc.php
317 ms
footer.png
2602 ms
likebox.php
189 ms
kyEKgjk51ZE.css
196 ms
xgj7bXhJNEH.css
237 ms
q68gy-v_YMF.js
317 ms
FJmpeSpHpjS.js
394 ms
0wM5s1Khldu.js
314 ms
1bNoFZUdlYZ.js
315 ms
flagsprites.png
46 ms
1800197_426371840827974_2074713038_n.jpg
221 ms
65496_259586907506469_743542824_n.jpg
294 ms
12802975_134243133632378_3216917443682237340_n.jpg
374 ms
314607_224184120982390_563101447_n.jpg
340 ms
12669450_1260745637275090_2316920485661058537_n.jpg
340 ms
wL6VQj7Ab77.png
53 ms
s7jcwEQH7Sx.png
53 ms
I6-MnjEovm5.js
45 ms
pQrUxxo5oQp.js
44 ms
srt.co.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
<frame> or <iframe> elements do not have a title
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
srt.co.th 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
srt.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 doesn't use legible font sizes
Tap targets are not sized appropriately
TH
EN
WINDOWS-874
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Srt.co.th can be misinterpreted by Google and other search engines. Our service has detected that Thai is used on the page, and it does not match the claimed English language. Our system also found out that Srt.co.th main page’s claimed encoding is windows-874. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
srt.co.th
Open Graph description is not detected on the main page of SRT. 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: