Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pruthai.com

Pruthai

Page Load Speed

822 ms in total

First Response

102 ms

Resources Loaded

606 ms

Page Rendered

114 ms

pruthai.com screenshot

About Website

Visit pruthai.com now to see the best up-to-date Pruthai content for United States and also check out these interesting facts you probably never knew about pruthai.com

pruthai

Visit pruthai.com

Key Findings

We analyzed Pruthai.com page load time and found that the first response time was 102 ms and then it took 720 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

pruthai.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

www.pruthai.com

102 ms

B4vL7jSlQUyZw1gmnRZM12Se_JgDZLDX9xwIZh1mbpvfecvJXnX1IyvhF2jtFRZLFR9tF29kZeIDZQBqZAJDZc9XjQZqwcZye6MK2hyydY8yScblZe8DSeUypPGHf5A5MyMMeMw6MKGHf5h5MyMMeMS6MKGHf5-5MyMMeMX6MKGHf5E5MyMMegI6MTMgcSfNn3j.js

100 ms

css2

91 ms

legacy.js

94 ms

modern.js

114 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Pruthai.com, 41% (9 requests) were made to Assets.squarespace.com and 23% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (270 ms) relates to the external source Assets.squarespace.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (34%)

Content Size

3.3 MB

After Optimization

2.2 MB

In fact, the total size of Pruthai.com main page is 3.3 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. 70% of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 88.6 kB

  • Original 104.7 kB
  • After minification 97.1 kB
  • After compression 16.1 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 88.6 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. Pruthai images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 1.0 MB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 976.0 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 1.0 MB or 52% of the original size.

CSS Optimization

-16%

Potential reduce by 3.1 kB

  • Original 19.2 kB
  • After minification 19.2 kB
  • After compression 16.1 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. Pruthai.com needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (59%)

Requests Now

17

After Optimization

7

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pruthai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

pruthai.com accessibility score

97

Accessibility Issues

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

pruthai.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pruthai.com SEO score

93

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pruthai.com 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), while the claimed language is English. Our system also found out that Pruthai.com 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.

Social Sharing Optimization

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