2.9 sec in total
1.4 sec
1.4 sec
86 ms
Welcome to database.dgr.go.th homepage info - get ready to check Database Dgr best content for Thailand right away, or after learning these important things about database.dgr.go.th
Visit database.dgr.go.thWe analyzed Database.dgr.go.th page load time and found that the first response time was 1.4 sec and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
database.dgr.go.th performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value1.2 s
100/100
25%
Value2.2 s
99/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
1393 ms
Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Database.dgr.go.th and no external sources were called. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Database.dgr.go.th.
Page size can be reduced by 62 B (65%)
95 B
33 B
In fact, the total size of Database.dgr.go.th main page is 95 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 95 B which makes up the majority of the site volume.
Potential reduce by 62 B
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 56 B, which is 59% 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 62 B or 65% of the original size.
We found no issues to fix!
0
0
Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.
database.dgr.go.th
1393 ms
database.dgr.go.th accessibility score
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
database.dgr.go.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
database.dgr.go.th SEO score
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Database.dgr.go.th 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 Database.dgr.go.th main page’s claimed encoding is . 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.
database.dgr.go.th
Open Graph description is not detected on the main page of Database Dgr. 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: