9.6 sec in total
1 sec
6.7 sec
1.9 sec
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.comWe 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.
yam.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value8.6 s
1/100
25%
Value12.2 s
3/100
10%
Value2,190 ms
6/100
30%
Value0.296
40/100
15%
Value15.4 s
7/100
10%
1038 ms
1317 ms
35 ms
1489 ms
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 size can be reduced by 147.4 kB (3%)
4.6 MB
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.
Potential reduce by 92.0 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.
Potential reduce by 54.3 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. Yam images are well optimized though.
Potential reduce by 1.2 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.
Number of requests can be reduced by 35 (24%)
144
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.
yam.com
1038 ms
www.yam.com
1317 ms
all.min.css
35 ms
css
1489 ms
adsbygoogle.js
114 ms
jquery-3.6.2.min.js
33 ms
swiper-bundle.min.js
39 ms
home
1009 ms
js
77 ms
h.png
1566 ms
w=638
314 ms
w=638
525 ms
w=638
532 ms
w=638
610 ms
w=638
610 ms
w=638
607 ms
w=638
605 ms
w=638
811 ms
w=638
689 ms
w=638
685 ms
w=638
690 ms
w=638
687 ms
w=638
687 ms
w=312,h=203,fit=cover
802 ms
w=312,h=203,fit=cover
801 ms
w=312,h=203,fit=cover
802 ms
w=312,h=203,fit=cover
802 ms
w=312,h=203,fit=cover
802 ms
w=340,h=200,fit=cover
879 ms
w=340,h=200,fit=cover
820 ms
w=340,h=200,fit=cover
824 ms
w=340,h=200,fit=cover
830 ms
w=340,h=200,fit=cover
830 ms
w=340,h=200,fit=cover
879 ms
w=340,h=200,fit=cover
834 ms
w=340,h=200,fit=cover
840 ms
w=340,h=200,fit=cover
841 ms
w=340,h=200,fit=cover
836 ms
w=340,h=200,fit=cover
849 ms
w=340,h=200,fit=cover
852 ms
w=340,h=200,fit=cover
855 ms
w=340,h=200,fit=cover
867 ms
w=340,h=200,fit=cover
864 ms
w=340,h=200,fit=cover
868 ms
w=340,h=200,fit=cover
881 ms
w=340,h=200,fit=cover
970 ms
logo.png
144 ms
footerLogo.png
521 ms
fa-solid-900.ttf
93 ms
fa-regular-400.ttf
233 ms
slotcar_library.js
177 ms
show_ads_impl.js
416 ms
beacon.js
157 ms
w=340,h=200,fit=cover
527 ms
f9hn5ppphe
429 ms
js
166 ms
w=340,h=200,fit=cover
366 ms
w=340,h=200,fit=cover
462 ms
w=400,h=400,fit=cover
299 ms
w=400,h=400,fit=cover
293 ms
w=400,h=400,fit=cover
299 ms
zrt_lookup.html
187 ms
ads
634 ms
w=400,h=400,fit=cover
234 ms
ads
442 ms
w=400,h=400,fit=cover
243 ms
w=400,h=400,fit=cover
239 ms
w=400,h=400,fit=cover
306 ms
w=400,h=400,fit=cover
235 ms
w=400,h=400,fit=cover
182 ms
ads
341 ms
w=400,h=400,fit=cover
170 ms
w=400,h=400,fit=cover
166 ms
w=400,h=400,fit=cover
174 ms
w=400,h=400,fit=cover
170 ms
w=400,h=400,fit=cover
170 ms
clarity.js
12 ms
w=400,h=400,fit=cover
273 ms
w=400,h=400,fit=cover
312 ms
w=640,h=360,fit=cover
154 ms
w=640,h=360,fit=cover
152 ms
w=640,h=360,fit=cover
169 ms
w=640,h=360,fit=cover
165 ms
w=640,h=360,fit=cover
167 ms
w=640,h=360,fit=cover
176 ms
w=640,h=360,fit=cover
360 ms
w=640,h=360,fit=cover
162 ms
w=640,h=360,fit=cover
169 ms
w=640,h=360,fit=cover
183 ms
w=640,h=360,fit=cover
167 ms
w=640,h=360,fit=cover
179 ms
w=640,h=360,fit=cover
179 ms
w=640,h=360,fit=cover
177 ms
w=640,h=360,fit=cover
186 ms
w=640,h=360,fit=cover
187 ms
w=640,h=360,fit=cover
195 ms
w=640,h=360,fit=cover
200 ms
w=640,h=360,fit=cover
192 ms
w=640,h=360,fit=cover
186 ms
w=640,h=360,fit=cover
495 ms
w=640,h=360,fit=cover
197 ms
w=640,h=360,fit=cover
185 ms
w=640,h=360,fit=cover
182 ms
w=640,h=360,fit=cover
317 ms
w=640,h=360,fit=cover
168 ms
w=640,h=360,fit=cover
165 ms
w=640,h=360,fit=cover
184 ms
w=640,h=360,fit=cover
248 ms
w=640,h=360,fit=cover
175 ms
w=640,h=360,fit=cover
188 ms
w=640,h=360,fit=cover
195 ms
w=640,h=360,fit=cover
198 ms
w=640,h=360,fit=cover
204 ms
w=640,h=360,fit=cover
207 ms
w=640,h=360,fit=cover
214 ms
reactive_library.js
153 ms
ca-pub-2675037296853968
108 ms
load_preloaded_resource.js
71 ms
icon.png
32 ms
abg_lite.js
60 ms
s
32 ms
window_focus.js
287 ms
qs_click_protection.js
73 ms
ufs_web_display.js
32 ms
bbcd6bf18c20baa1b2adeb195de9b551.js
65 ms
fullscreen_api_adapter.js
344 ms
interstitial_ad_frame.js
344 ms
pixel
353 ms
12626800242159903222
372 ms
abg_lite.js
43 ms
omrhp.js
44 ms
Q12zgMmT.js
343 ms
441 ms
feedback_grey600_24dp.png
340 ms
settings_grey600_24dp.png
360 ms
gen_204
338 ms
css
208 ms
pixel
154 ms
pixel
151 ms
62bHydCX.html
66 ms
activeview
135 ms
WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js
11 ms
51 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
191 ms
bounce
18 ms
rum
29 ms
pixel
21 ms
pixel
15 ms
rum
43 ms
sodar
72 ms
sodar2.js
21 ms
runner.html
33 ms
aframe
35 ms
c.gif
31 ms
yam.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
yam.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
yam.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
JA
ZH
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.
yam.com
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: