Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

thomaspaul.com

ThomasPaul | Designer Handmade Home Textile & Decor Products

Page Load Speed

4.7 sec in total

First Response

125 ms

Resources Loaded

3.9 sec

Page Rendered

701 ms

thomaspaul.com screenshot

About Website

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

Discover thomaspaul handmade textiles, candles, shower curtains and designer products! Everything to furnish your home in a vintage-inspired, modern way. Visit our site today!

Visit thomaspaul.com

Key Findings

We analyzed Thomaspaul.com page load time and found that the first response time was 125 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

thomaspaul.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value3,840 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.883

3/100

15%

TTI (Time to Interactive)

Value40.1 s

0/100

10%

Network Requests Diagram

shopthomaspaul.com

125 ms

shopthomaspaul.com

2191 ms

theme-bundle.polyfills.js

107 ms

theme-bundle.head_async.js

108 ms

css

115 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thomaspaul.com, 7% (4 requests) were made to Shopthomaspaul.com and 5% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Shopthomaspaul.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 666.7 kB (2%)

Content Size

29.0 MB

After Optimization

28.3 MB

In fact, the total size of Thomaspaul.com main page is 29.0 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. Only a small number of websites need less resources to load. Images take 28.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 327.9 kB

  • Original 371.0 kB
  • After minification 346.1 kB
  • After compression 43.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 327.9 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 313.6 kB

  • Original 28.4 MB
  • After minification 28.1 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. Thomas Paul images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 25.1 kB

  • Original 162.4 kB
  • After minification 158.0 kB
  • After compression 137.2 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 25.1 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (57%)

Requests Now

54

After Optimization

23

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

Accessibility Review

thomaspaul.com accessibility score

94

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

thomaspaul.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

thomaspaul.com SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thomaspaul.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Thomaspaul.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 Thomas Paul. 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: