Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

teapot.com.tw

普洱茶,大時代普洱壺藝茶行,普旺普洱茶,彥記陶苑,普洱茶批發,千年古樹茶,普洱品牌,台中市專賣古樹普洱茶,紫砂壺,朱泥壺

Page Load Speed

75.9 sec in total

First Response

3.5 sec

Resources Loaded

71.6 sec

Page Rendered

829 ms

teapot.com.tw screenshot

About Website

Welcome to teapot.com.tw homepage info - get ready to check Teapot best content for Taiwan right away, or after learning these important things about teapot.com.tw

本公司經營30年創立彥記陶苑堅持對茶壺泥料高品質,宜興自設煉泥廠,泥料精純無毒無化工,生產純原礦紫砂壺,朱泥壺,緞泥壺,紅泥壺,名家壺,雕刻壺泡茶好喝的茶壺。普旺茶業精選高端普洱茶生態茶、宮廷普洱熟茶、大樹純料千年古樹普洱生茶,雲南茶山頭春茶~邦崴茶王樹,景邁,臨滄大雪山,易武,冰島,昔歸,布朗,南糯,攸樂,老班章,普洱茶品牌~中茶牌,猛海茶廠,昆明茶廠,下關茶廠寶焰牌,大益

Visit teapot.com.tw

Key Findings

We analyzed Teapot.com.tw page load time and found that the first response time was 3.5 sec and then it took 72.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 39 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

teapot.com.tw performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

teapot.com.tw

3462 ms

teapot_index.css

785 ms

jquery-ui.css

88 ms

jquery-1.9.1.js

176 ms

jquery-ui.js

204 ms

Our browser made a total of 182 requests to load all elements on the main page. We found that 78% of them (142 requests) were addressed to the original Teapot.com.tw, 4% (7 requests) were made to Translate.googleapis.com and 2% (4 requests) were made to V3.jiathis.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Teapot.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 454.1 kB (4%)

Content Size

12.8 MB

After Optimization

12.4 MB

In fact, the total size of Teapot.com.tw main page is 12.8 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. 50% of websites need less resources to load. Images take 12.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 211.7 kB

  • Original 246.1 kB
  • After minification 199.0 kB
  • After compression 34.4 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. This page needs HTML code to be minified as it can gain 47.1 kB, which is 19% 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 211.7 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 144.1 kB

  • Original 12.3 MB
  • After minification 12.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. Teapot images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 24.9 kB

  • Original 127.6 kB
  • After minification 125.9 kB
  • After compression 102.7 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 24.9 kB or 19% of the original size.

CSS Optimization

-80%

Potential reduce by 73.4 kB

  • Original 91.4 kB
  • After minification 81.9 kB
  • After compression 18.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. Teapot.com.tw needs all CSS files to be minified and compressed as it can save up to 73.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (20%)

Requests Now

138

After Optimization

111

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

Accessibility Review

teapot.com.tw accessibility score

57

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

teapot.com.tw 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

Page has valid source maps

SEO Factors

teapot.com.tw SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teapot.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Teapot.com.tw 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 Teapot. 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: