Tools & Wizards About Us
why3s.cc screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 95

    SEO

    Google-friendlier than
    91% of websites

why3s.cc

WantEasy 網易資訊 官網 | 提供虛擬主機、網站空間、網域網址

Page Load Speed

8.9 sec in total

First Response

547 ms

Resources Loaded

8.2 sec

Page Rendered

158 ms

why3s.cc screenshot

About Website

Click here to check amazing Why 3 S content for Taiwan. Otherwise, check out these important facts you probably never knew about why3s.cc

網易開始於2003年，專注於台灣虛擬主機、美國虛擬主機、網域註冊、網址轉移，適合放置公司網站、WordPress部落格。也提供免費試用虛擬主機、免費網站搬家、免費75天備份。

Visit why3s.cc

Key Findings

We analyzed Why3s.cc page load time and found that the first response time was 547 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

why3s.cc performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

why3s.cc

547 ms

wanteasy.tw

1124 ms

system.css

641 ms

moo_maximenuhck.css

643 ms

maximenuhck.php

681 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Why3s.cc, 94% (34 requests) were made to Wanteasy.tw and 3% (1 request) were made to Check.why3s.com.tw. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Wanteasy.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 748.9 kB (49%)

Content Size

1.5 MB

After Optimization

790.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Why3s.cc main page is 1.5 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. Javascripts take 968.6 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 12.0 kB

  • Original 16.1 kB
  • After minification 14.1 kB
  • After compression 4.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 2.0 kB, which is 13% 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 12.0 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 15.3 kB

  • Original 510.1 kB
  • After minification 494.8 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. Why 3 S images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 684.8 kB

  • Original 968.6 kB
  • After minification 952.7 kB
  • After compression 283.8 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 684.8 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 36.9 kB

  • Original 44.1 kB
  • After minification 32.5 kB
  • After compression 7.2 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. Why3s.cc needs all CSS files to be minified and compressed as it can save up to 36.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (50%)

Requests Now

34

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why 3 S. 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 from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

why3s.cc

why3s.cc

547 ms

wanteasy.tw

wanteasy.tw

1124 ms

system.css

system.css

641 ms

moo_maximenuhck.css

moo_maximenuhck.css

643 ms

maximenuhck.php

maximenuhck.php

681 ms

beez_20-position1.css

beez_20-position1.css

672 ms

mootools-core.js

mootools-core.js

2617 ms

core.js

core.js

689 ms

caption.js

caption.js

1379 ms

mootools-more.js

mootools-more.js

2453 ms

moomaximenuck.js

moomaximenuck.js

2268 ms

style.css

style.css

2275 ms

slider.css

slider.css

2307 ms

video.css

video.css

2317 ms

jquery.1.6.4.min.js

jquery.1.6.4.min.js

3119 ms

global.merged.min.js

global.merged.min.js

3857 ms

jquery.jcarousel.js

jquery.jcarousel.js

2942 ms

modernizr.custom.89698.js

modernizr.custom.89698.js

2971 ms

script.js

script.js

3087 ms

system.css

system.css

2615 ms

headerconbg.png

headerconbg.png

341 ms

logo.png

logo.png

635 ms

searchbg.png

searchbg.png

634 ms

searchbtn.png

searchbtn.png

639 ms

wanteasy-offer-cheap-taiwan-usa-server.png

wanteasy-offer-cheap-taiwan-usa-server.png

2163 ms

bannerh1.png

bannerh1.png

1033 ms

ordernowbtn.png

ordernowbtn.png

1171 ms

wanteasy-offer-stable-server-slider.jpg

wanteasy-offer-stable-server-slider.jpg

1477 ms

wanteasy-offer-reliable-service-slider.jpg

wanteasy-offer-reliable-service-slider.jpg

1478 ms

wanteasy-help-you-move-site-free.jpg

wanteasy-help-you-move-site-free.jpg

1761 ms

wanteasy-slider-thumbnail-cheap-server.png

wanteasy-slider-thumbnail-cheap-server.png

1724 ms

wanteasy-slider-thumbnail-stable-server.jpg

wanteasy-slider-thumbnail-stable-server.jpg

1864 ms

wanteasy-slider-thumbnail-reliable-service.jpg

wanteasy-slider-thumbnail-reliable-service.jpg

2116 ms

wanteasy-help-you-move-site-free-slider-thumbnail.jpg

wanteasy-help-you-move-site-free-slider-thumbnail.jpg

2140 ms

piwik.js

piwik.js

1251 ms

carousel-button-sprite.png

carousel-button-sprite.png

1766 ms

Accessibility Review

why3s.cc accessibility score

96

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

why3s.cc best practices score

83

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

SEO Factors

why3s.cc SEO score

95

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

why3s.cc

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