Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 55% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 91

    SEO

    Google-friendlier than
    76% of websites

htg2.net

htg2.net

Page Load Speed

2.7 sec in total

First Response

862 ms

Resources Loaded

1.8 sec

Page Rendered

84 ms

htg2.net screenshot

About Website

Click here to check amazing Htg 2 content for Thailand. Otherwise, check out these important facts you probably never knew about htg2.net

Visit htg2.net

Key Findings

We analyzed Htg2.net page load time and found that the first response time was 862 ms and then it took 1.9 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.

Performance Metrics

htg2.net performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value4.0 s

87/100

10%

Network Requests Diagram

index.php

862 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 Htg2.net and no external sources were called. The less responsive or slowest element that took the longest time to load (862 ms) belongs to the original domain Htg2.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 299 B (42%)

Content Size

720 B

After Optimization

421 B

In fact, the total size of Htg2.net main page is 720 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 720 B which makes up the majority of the site volume.

HTML Optimization

-42%

Potential reduce by 299 B

  • Original 720 B
  • After minification 718 B
  • After compression 421 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. 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 299 B or 42% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

htg2.net accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Links do not have a discernible name

Best Practices

htg2.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

htg2.net SEO score

91

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Htg2.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Htg2.net main page’s claimed encoding is iso-8859-1. 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Htg 2. 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: