Tools & Wizards About Us
2006tw.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

2006tw.com

支付寶代付台灣支付寶代購【火速科技】

Page Load Speed

23.6 sec in total

First Response

1.3 sec

Resources Loaded

22 sec

Page Rendered

294 ms

2006tw.com screenshot

About Website

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

火速科技全台首家最專業代付支付寶,支付寶代購,代充支付寶,淘寶代購,人民幣貨款代付,全台最先開放5分鐘快速入賬,安全快捷省錢省心NO1

Visit 2006tw.com

Key Findings

We analyzed 2006tw.com page load time and found that the first response time was 1.3 sec and then it took 22.3 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.

Performance Metrics

2006tw.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

2006tw.com

1262 ms

bootstrap.css

1682 ms

bootstrap-responsive.css

1107 ms

base.css

886 ms

style.css

883 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 56% of them (24 requests) were addressed to the original 2006tw.com, 9% (4 requests) were made to Kefu.qycn.com and 9% (4 requests) were made to Img3.tbcdn.cn. The less responsive or slowest element that took the longest time to load (11.6 sec) relates to the external source Kefu.qycn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 310.2 kB (28%)

Content Size

1.1 MB

After Optimization

799.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 2006tw.com main page is 1.1 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. 25% of websites need less resources to load. Images take 736.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 35.4 kB

  • Original 43.6 kB
  • After minification 34.5 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 21% 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 35.4 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 16.4 kB

  • Original 736.0 kB
  • After minification 719.6 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. 2006 Tw images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 101.3 kB

  • Original 147.4 kB
  • After minification 140.5 kB
  • After compression 46.1 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 101.3 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 157.0 kB

  • Original 182.9 kB
  • After minification 141.6 kB
  • After compression 25.9 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. 2006tw.com needs all CSS files to be minified and compressed as it can save up to 157.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

42

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2006tw.com

2006tw.com

1262 ms

bootstrap.css

bootstrap.css

1682 ms

bootstrap-responsive.css

bootstrap-responsive.css

1107 ms

base.css

base.css

886 ms

style.css

style.css

883 ms

jquery-2.0.3.min.js

jquery-2.0.3.min.js

1764 ms

bootstrap.min.js

bootstrap.min.js

880 ms

jquery.cookie.js

jquery.cookie.js

1110 ms

layer.js

layer.js

1118 ms

491893.js

491893.js

919 ms

window.js

window.js

683 ms

state.php

state.php

7480 ms

bg.jpg

bg.jpg

260 ms

layer.css

layer.css

286 ms

logo.jpg

logo.jpg

218 ms

2.jpg

2.jpg

222 ms

public.gif

public.gif

225 ms

1.jpg

1.jpg

216 ms

TB18ZzIJXXXXXaTXpXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB18ZzIJXXXXXaTXpXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

492 ms

TB1_f2kJVXXXXX8XXXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1_f2kJVXXXXX8XXXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

828 ms

TB1cs3tGVXXXXblaXXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1cs3tGVXXXXblaXXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

852 ms

TB1VMhIJVXXXXX7XXXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1VMhIJVXXXXX7XXXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

859 ms

1.jpg

1.jpg

427 ms

2.jpg

2.jpg

651 ms

3.jpg

3.jpg

811 ms

4.jpg

4.jpg

648 ms

tel.jpg

tel.jpg

434 ms

TB1_A1ALpXXXXauapXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1_A1ALpXXXXauapXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

860 ms

TB1gtNUJpXXXXbpXVXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1gtNUJpXXXXbpXVXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

839 ms

TB10UvvKpXXXXc0XFXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB10UvvKpXXXXc0XFXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

842 ms

TB1wp12KpXXXXciXFXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1wp12KpXXXXciXFXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

827 ms

TB2Wkq4jFXXXXaBXpXXXXXXXXXX_!!2002648625.jpg_230x230.jpg

TB2Wkq4jFXXXXaBXpXXXXXXXXXX_!!2002648625.jpg_230x230.jpg

910 ms

TB1LjH7KVXXXXbBXVXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1LjH7KVXXXXbBXVXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

849 ms

TB1pWpZIFXXXXbuXXXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1pWpZIFXXXXbuXXXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

369 ms

TB1om4HJVXXXXaTXpXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

TB1om4HJVXXXXaTXpXXXXXXXXXX_!!0-item_pic.jpg_230x230.jpg

415 ms

x.jpg

x.jpg

285 ms

ibox.jpg

ibox.jpg

522 ms

flogo.jpg

flogo.jpg

489 ms

icon_0.gif

icon_0.gif

746 ms

icon.css

icon.css

9370 ms

miniDecoration.css

miniDecoration.css

5974 ms

main_new.js

main_new.js

11589 ms

vclient.js

vclient.js

1665 ms

Accessibility Review

2006tw.com accessibility score

70

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

Best Practices

2006tw.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

2006tw.com SEO score

85

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

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

2006tw.com

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