Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

pttco.org

PTTCO Bangkok Thailand IWCF Drilling & Intervention Well Control

Page Load Speed

1.3 sec in total

First Response

351 ms

Resources Loaded

582 ms

Page Rendered

363 ms

pttco.org screenshot

About Website

Visit pttco.org now to see the best up-to-date PTTCO content and also check out these interesting facts you probably never knew about pttco.org

IWCF/IADC well control School, IWCF/IADC WellCAP Pattaya, IWCF Well Intervention Well Control at Bangkok, IWCF/IADC Well Services Certification Training at KL Kuala Lumpur Malaysia, Jakarta Indonesia,...

Visit pttco.org

Key Findings

We analyzed Pttco.org page load time and found that the first response time was 351 ms and then it took 945 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

pttco.org performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

99/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

pttco.org

351 ms

clipart13.jpg

109 ms

navbar-0-active-97458.png

108 ms

navbar-1-inactive-97505.png

106 ms

navbar-2-inactive-97567.png

101 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that all of those requests were addressed to Pttco.org and no external sources were called. The less responsive or slowest element that took the longest time to load (351 ms) belongs to the original domain Pttco.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 300.2 kB (74%)

Content Size

406.0 kB

After Optimization

105.8 kB

In fact, the total size of Pttco.org main page is 406.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. 25% of websites need less resources to load. HTML takes 244.2 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 225.5 kB

  • Original 244.2 kB
  • After minification 220.5 kB
  • After compression 18.7 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 225.5 kB or 92% of the original size.

Image Optimization

-46%

Potential reduce by 74.7 kB

  • Original 161.8 kB
  • After minification 87.1 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. Obviously, PTTCO needs image optimization as it can save up to 74.7 kB or 46% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

21

After Optimization

21

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PTTCO. According to our analytics all requests are already optimized.

Accessibility Review

pttco.org 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

pttco.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

pttco.org SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pttco.org 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 Pttco.org 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.

Social Sharing Optimization

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