Tools & Wizards About Us
whosee.com screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

whosee.com

胡賜益的首頁

Page Load Speed

5.7 sec in total

First Response

2.3 sec

Resources Loaded

3.1 sec

Page Rendered

265 ms

whosee.com screenshot

About Website

Click here to check amazing Whosee content. Otherwise, check out these important facts you probably never knew about whosee.com

Visit whosee.com

Key Findings

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

Performance Metrics

whosee.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

whosee.com

2298 ms

left.html

152 ms

top.html

156 ms

main.html

162 ms

b_00.jpg

231 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Whosee.com and no external sources were called. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Whosee.com.

Page Optimization Overview & Recommendations

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

Content Size

65.2 kB

After Optimization

62.4 kB

  • HTML
  • Images

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

HTML Optimization

-51%

Potential reduce by 288 B

  • Original 564 B
  • After minification 468 B
  • After compression 276 B

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 96 B, which is 17% 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 288 B or 51% of the original size.

Image Optimization

-4%

Potential reduce by 2.5 kB

  • Original 64.6 kB
  • After minification 62.1 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. Whosee images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

26

After Optimization

26

  • AJAX
  • Images

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whosee. According to our analytics all requests are already optimized.

Network Requests Diagram

whosee.com

whosee.com

2298 ms

left.html

left.html

152 ms

top.html

top.html

156 ms

main.html

main.html

162 ms

b_00.jpg

b_00.jpg

231 ms

b_01.gif

b_01.gif

231 ms

b_02.gif

b_02.gif

161 ms

b_03.gif

b_03.gif

163 ms

b_04.gif

b_04.gif

163 ms

b_05.gif

b_05.gif

160 ms

b_06.gif

b_06.gif

260 ms

b_07.gif

b_07.gif

260 ms

b_08.gif

b_08.gif

259 ms

b_09.gif

b_09.gif

260 ms

b_10.gif

b_10.gif

302 ms

b_11.gif

b_11.gif

450 ms

nh23_email_1.gif

nh23_email_1.gif

479 ms

top.jpg

top.jpg

435 ms

m_01.jpg

m_01.jpg

617 ms

b_02-a.gif

b_02-a.gif

76 ms

b_03-a.gif

b_03-a.gif

86 ms

b_04-a.gif

b_04-a.gif

79 ms

b_05-a.gif

b_05-a.gif

79 ms

b_06-a.gif

b_06-a.gif

80 ms

b_07-a.gif

b_07-a.gif

140 ms

b_08-a.gif

b_08-a.gif

149 ms

b_10-a.gif

b_10-a.gif

151 ms

Accessibility Review

whosee.com accessibility score

33

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

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

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

Best Practices

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

SEO Factors

whosee.com SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whosee.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Whosee.com main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

whosee.com

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