34 sec in total
1.4 sec
31.6 sec
933 ms
Welcome to trueid.net homepage info - get ready to check Trueid best content for Thailand right away, or after learning these important things about trueid.net
Visit trueid.netWe analyzed Trueid.net page load time and found that the first response time was 1.4 sec and then it took 32.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
trueid.net performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value19.8 s
0/100
25%
Value11.9 s
4/100
10%
Value4,400 ms
1/100
30%
Value1.009
2/100
15%
Value32.0 s
0/100
10%
1448 ms
1216 ms
1206 ms
311 ms
592 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 91% of them (42 requests) were addressed to the original Trueid.net, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Sso.trueid.net.
Page size can be reduced by 42.9 kB (58%)
74.0 kB
31.2 kB
In fact, the total size of Trueid.net main page is 74.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 53.0 kB which makes up the majority of the site volume.
Potential reduce by 42.8 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 42.8 kB or 81% of the original size.
Potential reduce by 50 B
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.
Number of requests can be reduced by 15 (36%)
42
27
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trueid. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
trueid.net
1448 ms
about
1216 ms
custom.css
1206 ms
addon.css
311 ms
modernizr.js
592 ms
jquery-1.8.3.min.js
2053 ms
bootstrap.min.js
1169 ms
transition.js
878 ms
scrollspy.js
875 ms
modal.js
1267 ms
retina.js
1171 ms
trueid-sso-widget.js
2359 ms
modernizr_custom.js
1805 ms
jqueryscrollto.js
1486 ms
jqueryscrollto_custom.js
1501 ms
trueidlogo.png
637 ms
th.png
557 ms
hand_id.png
2754 ms
store_apple.png
1136 ms
store_play.png
1202 ms
icon01.png
1215 ms
icon02.png
1450 ms
icon03.png
1796 ms
icon04.png
1803 ms
icon05.png
1811 ms
hand_connected.png
2820 ms
icon_privilege.png
2128 ms
hand_ipad.png
2732 ms
gtm.js
272 ms
slogan_bg.jpg
2391 ms
bg_whatistrueid.jpg
2745 ms
bg_connected.jpg
2770 ms
bg_register.jpg
2733 ms
register_dot.png
2995 ms
icon_register.png
3280 ms
bg_helpandsupport.jpg
4575 ms
btn_backtotop.png
3029 ms
tbold-webfont.woff
3270 ms
tmedium-webfont.woff
3227 ms
analytics.js
54 ms
collect
35 ms
widget.php
6329 ms
trueid-sso-receiver.min.js
903 ms
jquery.fancybox.css
646 ms
jquery.mousewheel-3.0.6.pack.js
289 ms
jquery.fancybox.js
563 ms
trueid.net 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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
trueid.net 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
trueid.net SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trueid.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Trueid.net 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.
trueid.net
Open Graph description is not detected on the main page of Trueid. 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: