Tools & Wizards About Us
yohoboys.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

yohoboys.com

男生志 | Play & Learn ｜ Yoho!潮流志-Yoho!Now

Page Load Speed

9.9 sec in total

First Response

781 ms

Resources Loaded

8.7 sec

Page Rendered

394 ms

yohoboys.com screenshot

About Website

Visit yohoboys.com now to see the best up-to-date Yoho Boys content for Taiwan and also check out these interesting facts you probably never knew about yohoboys.com

Yoho!潮流志男生潮流专为爱潮流，爱时尚的男士提供潮流视频，时尚潮流，运动潮流，生活潮流，潮流杂志以及科普潮流百科，让您尽兴的了解并且深入学习潮流文化，想变为爱时尚的潮男就来Yoho!潮流志！

Visit yohoboys.com

Key Findings

We analyzed Yohoboys.com page load time and found that the first response time was 781 ms and then it took 9.1 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

yohoboys.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

yohoboys.com

781 ms

www.yohoboys.com

1474 ms

gtm.js

66 ms

boys.css

1711 ms

yas.js

338 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Yohoboys.com, 38% (19 requests) were made to Res.yohoboys.com and 18% (9 requests) were made to Imgboys1.yohobuy.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Res.yohoboys.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.9 kB (6%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 53.3 kB

  • Original 67.2 kB
  • After minification 60.9 kB
  • After compression 13.9 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 53.3 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 88.2 kB

  • Original 2.6 MB
  • After minification 2.5 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. Yoho Boys images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 91 B

  • Original 29.2 kB
  • After minification 29.2 kB
  • After compression 29.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. This website has mostly compressed JavaScripts.

CSS Optimization

-37%

Potential reduce by 16.3 kB

  • Original 43.5 kB
  • After minification 43.5 kB
  • After compression 27.3 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. Yohoboys.com needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (13%)

Requests Now

45

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yohoboys.com

yohoboys.com

781 ms

www.yohoboys.com

www.yohoboys.com

1474 ms

gtm.js

gtm.js

66 ms

boys.css

boys.css

1711 ms

yas.js

yas.js

338 ms

seajs.js

seajs.js

780 ms

02354935.boys.js

02354935.boys.js

3306 ms

y-logo.jpg

y-logo.jpg

74 ms

close20.png

close20.png

221 ms

ebsIcon.png

ebsIcon.png

74 ms

o_1d44bg0md1s5312a317d41nsg1m918.jpg

o_1d44bg0md1s5312a317d41nsg1m918.jpg

309 ms

logo.png

logo.png

253 ms

common-nav-s.jpg

common-nav-s.jpg

990 ms

submenubackground.png

submenubackground.png

503 ms

phone.png

phone.png

1378 ms

littleloading.gif

littleloading.gif

752 ms

searchbutton.png

searchbutton.png

996 ms

followusbackground.png

followusbackground.png

1239 ms

followus.png

followus.png

1247 ms

weixinbackground.png

weixinbackground.png

1489 ms

pager_choosen.png

pager_choosen.png

1498 ms

bottom_1080.png

bottom_1080.png

2240 ms

phone-icon.png

phone-icon.png

2557 ms

split-v.png

split-v.png

1738 ms

yohoboyqr.png

yohoboyqr.png

1747 ms

returntop.png

returntop.png

1985 ms

police.png

police.png

1996 ms

webfont.woff

webfont.woff

2404 ms

getnewest

getnewest

780 ms

analytics.js

analytics.js

19 ms

yas.js

yas.js

41 ms

0103f2d4a1afb78bf08def9021d82ee42a.jpg

0103f2d4a1afb78bf08def9021d82ee42a.jpg

879 ms

20230726012318322.jpg

20230726012318322.jpg

2744 ms

69d2201ab9854595aebd3b61cf02f49b.jpeg

69d2201ab9854595aebd3b61cf02f49b.jpeg

547 ms

022b8d7be6d38b64e560e065215a67d719.jpg

022b8d7be6d38b64e560e065215a67d719.jpg

1065 ms

01494d1ceb2b9f41340d4cf131065e481b.jpg

01494d1ceb2b9f41340d4cf131065e481b.jpg

638 ms

01b634ee2f8dd28661defa439d12d6f83e.jpg

01b634ee2f8dd28661defa439d12d6f83e.jpg

896 ms

collect

collect

28 ms

js

js

53 ms

948 ms

010d2c7029cf48f8a52f14d0ba370a2ee8.png

010d2c7029cf48f8a52f14d0ba370a2ee8.png

639 ms

01770bc0b69a947ed346c9f868e2a97688.jpg

01770bc0b69a947ed346c9f868e2a97688.jpg

463 ms

01a1ab72e578b3c5f3595f3c4bd28e41f8.png

01a1ab72e578b3c5f3595f3c4bd28e41f8.png

844 ms

01bb16090eaee23ec83a6fba800024ef85.jpg

01bb16090eaee23ec83a6fba800024ef85.jpg

482 ms

015897f6ebecb8be418929bde7a933d0be.jpg

015897f6ebecb8be418929bde7a933d0be.jpg

487 ms

0197dc5af426d5d17e7555a6e350fb10f1.jpg

0197dc5af426d5d17e7555a6e350fb10f1.jpg

733 ms

022727181637c9480338bac1f6c2c15dc3.jpg

022727181637c9480338bac1f6c2c15dc3.jpg

579 ms

02a0f1e31a35755e5ee476ecb9629815a7.png

02a0f1e31a35755e5ee476ecb9629815a7.png

918 ms

02a00c09da3cd41edbd14e086e4fa18d80.jpg

02a00c09da3cd41edbd14e086e4fa18d80.jpg

600 ms

293 ms

Accessibility Review

yohoboys.com accessibility score

56

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

yohoboys.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

SEO Factors

yohoboys.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

Links are not crawlable

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 Yohoboys.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 Yohoboys.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

yohoboys.com

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