Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

yam.com

yam 蕃薯藤

Page Load Speed

9.6 sec in total

First Response

1 sec

Resources Loaded

6.7 sec

Page Rendered

1.9 sec

About Website

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

天空傳媒(蕃薯藤),1997年成立,目前是台灣最大影音視頻網站、第二大入口網站;擁有天空部落、新聞財金、小蕃薯、揪團購、購物中心等多元頻道,點閱率超過一個半台灣人口數,是擁有入口、新聞、影音、社群、電子商務的全威力網路媒體。

Visit yam.com

Key Findings

We analyzed Yam.com page load time and found that the first response time was 1 sec and then it took 8.6 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

yam.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.296

40/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

yam.com

1038 ms

www.yam.com

1317 ms

all.min.css

35 ms

css

1489 ms

adsbygoogle.js

114 ms

Our browser made a total of 154 requests to load all elements on the main page. We found that 4% of them (6 requests) were addressed to the original Yam.com, 59% (91 requests) were made to Imagedelivery.net and 7% (11 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Weather.yam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 147.4 kB (3%)

Content Size

4.6 MB

After Optimization

4.5 MB

In fact, the total size of Yam.com main page is 4.6 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. Only a small number of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 92.0 kB

  • Original 112.7 kB
  • After minification 112.7 kB
  • After compression 20.7 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 92.0 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 54.3 kB

  • Original 4.0 MB
  • After minification 4.0 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. Yam images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 482.7 kB
  • After minification 482.7 kB
  • After compression 481.5 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.

Requests Breakdown

Number of requests can be reduced by 35 (24%)

Requests Now

144

After Optimization

109

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

Accessibility Review

yam.com accessibility score

77

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

yam.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

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

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yam.com 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 Chinese language. Our system also found out that Yam.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

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