2.6 sec in total
211 ms
1.7 sec
696 ms
Welcome to yahoo.hk homepage info - get ready to check Yahoo best content for Hong Kong right away, or after learning these important things about yahoo.hk
在Yahoo! 首頁,您可以一覽即時重要社會新聞、國際新知、娛樂消息、生活資訊;您更可以加入Yahoo! 會員計劃,天天累積點數,免費兌換禮物、美食、優惠券,著數多多!
Visit yahoo.hkWe analyzed Yahoo.hk page load time and found that the first response time was 211 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
yahoo.hk performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value6.2 s
11/100
25%
Value13.8 s
1/100
10%
Value5,720 ms
0/100
30%
Value0
100/100
15%
Value24.1 s
0/100
10%
211 ms
9 ms
1039 ms
40 ms
46 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yahoo.hk, 94% (115 requests) were made to S.yimg.com and 2% (3 requests) were made to Hk.yahoo.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Hk.yahoo.com.
Page size can be reduced by 414.5 kB (13%)
3.1 MB
2.7 MB
In fact, the total size of Yahoo.hk main page is 3.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 258.5 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 258.5 kB or 77% of the original size.
Potential reduce by 153.4 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. Yahoo images are well optimized though.
Potential reduce by 1.7 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.
Potential reduce by 910 B
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. Yahoo.hk has all CSS files already compressed.
Number of requests can be reduced by 58 (49%)
119
61
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yahoo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
yahoo.hk
211 ms
hk.yahoo.com
9 ms
hk.yahoo.com
1039 ms
homepage.e0481e6f6b2bf4df21cc1546fe590ad9.css
40 ms
bundle.c60a6d54.css
46 ms
modulecss.c87fbef256b2e85720c427bd4495b4e6.css
42 ms
fp-desktop.eeb294e5ac64725948120b9bdadcddc3.css
47 ms
colors_1.1.27.min.css
43 ms
react-wafer-footer.FooterDesktop.atomic.ltr.6f7623d26a63f89321b18d342673c9c6.min.css
46 ms
react-wafer-apac-header.HeaderDesktop.atomic.ltr.538ca49a130e12844753ecfa1281f24b.min.css
43 ms
react-wafer-apac-header.custom.desktop.5d0fa7537db5c07548f1e12d8723ad15.css
47 ms
react-wafer-weather.WeatherShortcutIntenseWidget.atomic.ltr.29ee052a7aa15eedf2b3d4a325e5b849.min.css
51 ms
react-wafer-weather.common.desktop.a03361886464b469acd3a16cfbd022ed.css
50 ms
tdv2-wafer-locker.Locker.atomic.ltr.fe6f478e7690f533baa709caca698aaa.min.css
48 ms
tdv2-wafer-locker.custom.0958471007d97d88f6c207738f0c6030.css
49 ms
tdv2-wafer-profile.Profile.atomic.ltr.e6e093aec5a69d195d63348085793314.min.css
55 ms
tdv2-wafer-loyalty.LoyaltyWidget.atomic.ltr.7f83b2a48e0a90f3e8f571730b221f24.min.css
53 ms
tdv2-wafer-loyalty.custom.10b43cbb23d8fdd38616b73b768daf56.css
53 ms
react-wafer-weather.WeatherWidget.atomic.ltr.ae02ae1355852bf0f61b77509ba08bee.min.css
56 ms
react-wafer-horoscope.HoroscopeWidget.atomic.ltr.d516c9456ae2ce7c57dacbe82cd35986.min.css
54 ms
react-wafer-featurebar.FeaturebarNew.atomic.ltr.1f38518fd23317c7e8f5c7313814f31b.min.css
57 ms
react-wafer-ntk.NTKTab.atomic.ltr.2e4572c35e8f9b4571eb0bc8b83dacf3.min.css
60 ms
react-wafer-stream.StreamTab.atomic.ltr.b5ac9202ca4b5de0d77555f5503d5b96.min.css
58 ms
react-wafer-apac-tv.TVDesktop.atomic.ltr.782a43d3be718b74bad831df7ee0a256.min.css
58 ms
react-wafer-apac-tv.custom.desktop.a1b3fe1280e8b9855efbf1a2d92d8af7.css
61 ms
tdv2-wafer-category.Category.atomic.ltr.fb6e4b2168c582b2b1448654424f2414.min.css
60 ms
cmp.js
84 ms
consent.js
65 ms
benji-2.1.44.js
69 ms
back_to_top.c336ea9e1b526dd4aac40381f3a11cd7.js
66 ms
handwriting.7238774aa05650a018ae0a61791d2126.js
66 ms
tab_hover_beaconclick.4590f384764b12e190af23ea35408120.js
69 ms
sticky.e40ed47b64bc6abcd0be99def7c7d907.js
65 ms
voice_search_lib_hk.ba3c9d30ca07c95c906b29f0aab707bc.js
69 ms
voice_search_init_hk.9b80f09d1203ac1b81ca9038a245d122.js
71 ms
wf-tabs-1.12.6.js
71 ms
wf-toggle-1.15.4.js
71 ms
wf-menu-1.3.1.js
71 ms
wf-fetch-1.19.1.js
72 ms
wf-rapid-1.10.8.js
72 ms
react-wafer-apac-header.custom.desktop.df1bb24ff2d87516d3adc851885405c9.js
42 ms
wf-autocomplete-1.31.8.js
39 ms
wf-form-1.34.5.js
38 ms
wf-geolocation-1.3.0.js
38 ms
wf-caas-1.36.5.js
38 ms
react-wafer-featurebar.custom.default.95a7979b4c06295e22960043d003fb49.js
37 ms
wf-beacon-1.3.4.js
37 ms
wf-video-3.1.2.js
35 ms
wf-benji-1.1.4.js
36 ms
wf-image-1.4.0.js
37 ms
wf-bind-1.1.3.js
36 ms
wf-text-1.2.0.js
36 ms
react-wafer-apac-tv.custom.desktop.5735e469394b333cdb06cf16f6a020cd.js
33 ms
Yahoo-HK-desktop-FP@2x.png
15 ms
pphw_sprites-775e15deb23bd2d4ff74723e324444a7.png
3 ms
Frontpage_left_banner__2_.png
4 ms
4631b0f0-14e6-11ef-8aed-96bd1c368b66
36 ms
690837b0-14bf-11ef-9f8b-eea82666a2b4
47 ms
2d72e5f62aec4c91dfbb24918d5b9739
45 ms
rapid-3.53.38.js
38 ms
benjiEventHandler.d8ecc617955f3972112167735b389e2b.js
39 ms
edgeToEdgeEventHandler.ed9bc02ae952b5fecfd87b9c0783b1ea.js
39 ms
yaft-0.3.29.min.js
39 ms
wf-core-1.65.1.js
40 ms
advertisement_0.0.19.js
41 ms
7eb7f250-14c2-11ef-bfd7-130147b52d08
41 ms
a53e71f0-134c-11ef-9bff-c65d86a9d340
60 ms
b22d3910-141d-11ef-abfc-eb33a449da14
61 ms
aea1b5c0-ea53-11ea-bffc-767b7391d286
41 ms
c6d38500-6004-11ed-af6e-40beea945859
42 ms
d1ae6950-14b1-11ef-bfe3-bb0f359cd6d9
44 ms
7f628970-142e-11ef-afdf-671b38208f91
49 ms
6b79c730-14af-11ef-9fed-053c8e178c9d
44 ms
c05c01b1-1427-11ef-bff9-8124fccda7f8
46 ms
1489af10-13e9-11ef-aed4-7e46fa43a294
47 ms
60bd0640-1365-11ef-bd7f-3c9221a499d3
54 ms
b8c2c140-1103-11ef-bee9-f9e375c9475a
49 ms
60d4bbc4bd95b0837ec6c3f41bcaf5ef
51 ms
468b50c380159342a552bff685d15808
53 ms
6d91ad6f3d5b37cbdd55746903da8b7b
55 ms
TW_desktop_tv_home.png
63 ms
a823b5a3f0b4e908dafffd4e90d9c103
60 ms
b38ab3126b74f8746716d701d9929c46
59 ms
image.jpg
59 ms
aa2f47a8e3ed64307c8bdff420cb6893
61 ms
7ac0e5f74f96324fc658d7357106edbf
60 ms
94d1b420-3770-11ee-a936-92e6cb7921a0
63 ms
bd96fab0-376f-11ee-9edf-70f7dbd949b8
63 ms
3ed29630-376f-11ee-b8d5-cb41392dae87
63 ms
47dd68e0-0b3c-11ee-afdd-aae806570dd5
64 ms
215eca20-efb6-11ed-ae75-4df81593dd06
65 ms
9fd51471-e58b-11ed-b7bf-8a0edd46901b
66 ms
82953420-de11-11ed-9fff-65df75355725
55 ms
e2f258c0-d82b-11ed-bb3b-e046f5d4f1b9
52 ms
010411d0-cdfc-11ed-be77-1fddc6a2c201
52 ms
7ac13520-c898-11ed-afdb-18aeb2059744
55 ms
e46d7730-c8ad-11ed-af67-f82f5f1bf1da
51 ms
778db660-c3e0-11ed-b199-4aea3069ec7b
52 ms
407ebee0-b723-11ed-b6dd-bd16d50be8e0
54 ms
79cbffb0-b02e-11ed-befe-35dcf41d9604
51 ms
163eb490-abb2-11ed-bb1f-d731ce3def1d
53 ms
4e254370-a931-11ed-bfbf-d8c5aaa811fb
53 ms
e190b430-a7cb-11ed-9ea7-20782ecebac4
54 ms
91811930-a7cb-11ed-b8fc-177c43f9a26a
53 ms
449a5710-a60b-11ed-af77-978dbc850bf1
52 ms
6856b430-a266-11ed-bb9f-d921c482520b
52 ms
stream_3840x2160x0_v2_3_0.jpg
52 ms
e5acd3d0-9a30-11ed-b5ce-9211405c103b
50 ms
db5eb5d1-987b-11ed-bbff-2e20d44f680c
49 ms
ee2e4840-957b-11ed-9fbd-bc1d64364caf
49 ms
ec30c8a0-925c-11ed-a7fc-60272d9852a1
48 ms
privacy-choice-control.png
47 ms
autoplay_default.png
48 ms
play-orb.png
49 ms
__rapid-worker-1.2.js
140 ms
cs_1.6.1.js
111 ms
evplayer.js
30 ms
p
108 ms
perf-vitals_3.2.0.js
11 ms
tv_hl_icon_beauty@2x.png
23 ms
p
109 ms
spinner-24x24-anim.gif
3 ms
yahoo.hk accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
yahoo.hk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
yahoo.hk SEO score
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 Yahoo.hk 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 Yahoo.hk 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.
yahoo.hk
Open Graph data is detected on the main page of Yahoo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: