Access yamedia.tw. yam 蕃薯藤

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value3,110 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.468

19/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

blog.yam.com

2098 ms

vipfooter.css

1052 ms

vipblog.css

1264 ms

custom.css

1058 ms

jquery.min.js

29 ms

Our browser made a total of 144 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yamedia.tw, 15% (22 requests) were made to Profile.yamedia.tw and 7% (10 requests) were made to Admd.yam.com. The less responsive or slowest element that took the longest time to load (5.8 sec) relates to the external source Pics9.yamedia.tw.

Content Size

9.9 MB

After Optimization

9.4 MB

In fact, the total size of Yamedia.tw main page is 9.9 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. 45% of websites need less resources to load. Images take 9.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 94.0 kB

Original 112.4 kB
After minification 103.6 kB
After compression 18.3 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 94.0 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 382.2 kB

Original 9.7 MB
After minification 9.3 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 Edia images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 47.9 kB

Original 87.7 kB
After minification 63.7 kB
After compression 39.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 47.9 kB or 55% of the original size.

CSS Optimization

-85%

Potential reduce by 27.3 kB

Original 32.3 kB
After minification 25.9 kB
After compression 5.0 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. Yamedia.tw needs all CSS files to be minified and compressed as it can save up to 27.3 kB or 85% of the original size.

Requests Now

143

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

High

robots.txt is not valid

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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 Yamedia.tw 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 Yamedia.tw 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

yamedia.tw

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

Report Summary

Performance

Accessibility

Best Practices

SEO

yam 蕃薯藤

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

blog.yam.com

vipfooter.css

vipblog.css

custom.css

jquery.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

blog.yam.com

vipfooter.css

vipblog.css

custom.css

jquery.min.js

jquery-ui.min.js

swfobject.js

admin_left_1.js

visit.php

footer_960_tv_utf8.js

js_global.js

pngfix.js

yam_AD_ajax.js

ya.js

atrk.js

beacon.js

menubar_all_01.gif

sindex.jpg

t_156d47880a08af.jpg

t_156d47604aa30a.jpg

t_156d476c804b65.jpg

t_156d478495ffae.jpg

t_156d47171bab4e.jpg

t_156d46d0e23f14.jpg

t_156d46933c3599.jpg

t_156d46a5126595.jpg

t_156d465f41425c.jpg

t_156d465b883b06.jpg

2010logo.jpg

search_btn.jpg

e-payment.png

buy_house.jpg

henji.png

page_white_edit.png

picture.png

konqsidebar_mediaplayer.png

internet-group-chat.png

josho.png

20150922154113ccb.jpg

20150824163757759.jpg

201502101521285ef.jpg

201502101523033be.jpg

20160202161143a16.jpg