11.5 sec in total
908 ms
10.2 sec
377 ms
Click here to check amazing I 1 content. Otherwise, check out these important facts you probably never knew about i1.hk
主頁 明鑄慈善基金, 香港「認可慈善捐款」的慈善機構
Visit i1.hkWe analyzed I1.hk page load time and found that the first response time was 908 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
i1.hk performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value6.4 s
10/100
25%
Value5.6 s
52/100
10%
Value2,180 ms
6/100
30%
Value0.001
100/100
15%
Value7.1 s
51/100
10%
908 ms
643 ms
432 ms
434 ms
434 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original I1.hk, 33% (44 requests) were made to Uwants.com and 3% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (6.1 sec) relates to the external source N2.hk.
Page size can be reduced by 1.4 MB (25%)
5.5 MB
4.1 MB
In fact, the total size of I1.hk main page is 5.5 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. 75% 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 4.1 MB which makes up the majority of the site volume.
Potential reduce by 87.4 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. This page needs HTML code to be minified as it can gain 16.4 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 87.4 kB or 77% of the original size.
Potential reduce by 438.8 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. Obviously, I 1 needs image optimization as it can save up to 438.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 611.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 611.8 kB or 65% of the original size.
Potential reduce by 245.8 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. I1.hk needs all CSS files to be minified and compressed as it can save up to 245.8 kB or 83% of the original size.
Number of requests can be reduced by 40 (35%)
113
73
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
index.php
908 ms
jquery-1.10.2.min.js
643 ms
common_rev09.js
432 ms
common_rev13.js
434 ms
menu.js
434 ms
ajax.js
439 ms
swfaddress.js
438 ms
jquery.fancybox.js
670 ms
jquery.fancybox.css
674 ms
jquery.sortable.min.js
675 ms
crystal.js
869 ms
nw_adserv.js
677 ms
style.css
674 ms
jquery-scrolltofixed.js
674 ms
jquery-ui.min.js
1080 ms
respond.js
860 ms
function.js
861 ms
top_bar_rev1501.css
864 ms
adsbygoogle.js
11 ms
lview
664 ms
ping_ud.js
679 ms
uwants_map_obj.js
676 ms
conversion.js
115 ms
beacon.js
71 ms
atrk.js
147 ms
fixed_logo.png
326 ms
iconfont-link.png
310 ms
top_btn_cricle.png
307 ms
iconfont-topmenu.png
308 ms
search-arrow.png
743 ms
spacer.gif
746 ms
uwants-interface-element.png
1159 ms
black-70.png
750 ms
mammydaddy.png
298 ms
mytour.png
294 ms
jetso.png
615 ms
price.png
615 ms
car.png
610 ms
playgame.hk_logo.png
734 ms
adhere.png
610 ms
logo.png
611 ms
60.gif
732 ms
2023.png
771 ms
2022.png
1059 ms
1992.png
1062 ms
2020.png
1062 ms
2015.png
1068 ms
2009.png
1070 ms
1940.png
1120 ms
1984.png
1124 ms
1955.png
1129 ms
1796.png
1131 ms
1838.png
1320 ms
1948.png
1323 ms
1812.png
1335 ms
2005.png
1335 ms
gid_dots_news.png
1339 ms
160310_b812a7cbc919b604db1228c9c9f06736
1555 ms
160308_202ecae479ca459f890c6d808ac739be
2170 ms
news-label.png
702 ms
home_icon_01.png
699 ms
home_icon_02.png
703 ms
home_icon_04.png
758 ms
home_icon_03_beta.png
719 ms
mobile_game.png
1048 ms
more_arrow.png
1048 ms
platform_list.png
1049 ms
line.jpg
1054 ms
icon_list.png
1058 ms
atrk.gif
191 ms
2506_23audh_11.jpg
1642 ms
2486_1e3926_1.jpg
1655 ms
2501_bebihf_1.jpg
1646 ms
2498_nau3m1_1.jpg
1438 ms
160316_7960ee7bfe281eefc7a9d0f990a79930
3596 ms
160316_a7da8bf470f88f04468428d8aae07022
2949 ms
160316_5976485390051e4c5dd9207ee160087b
2920 ms
160316_bc29adb859cb547593581513775b8019
3589 ms
160316_4b8ba41f5f8b1a454b67f8c8a15a097d
2942 ms
160316_9b2fae05ea7459b36d4ce4412bcee306
3119 ms
160316_90197d2a70c09da60f6d79da3a3bf55c
4772 ms
160316_7c52a02a0d152914b3ee6f325d4bbb87
4999 ms
160315_cadc1c743d66f67a209aca1a243b55cb
5436 ms
test.png
170 ms
videoseries
223 ms
ca-pub-5281467099397116.js
55 ms
zrt_lookup.html
50 ms
show_ads_impl.js
55 ms
beauty_clock.php
781 ms
sdk.js
165 ms
ga.js
116 ms
ads
1211 ms
osd.js
148 ms
__utm.gif
111 ms
www-embed-player-vflRGs1ko.css
250 ms
www-embed-player.js
316 ms
base.js
396 ms
182 ms
lview
501 ms
197 ms
144 ms
xd_arbiter.php
148 ms
xd_arbiter.php
363 ms
160316_751d351d9fc247bd0e5e13a152ce2373
4404 ms
160316_6e600b674f653df904bc32a9fe2f74e8
3659 ms
160316_429c948901fa53d20cc0b8e2d555f2d0
5070 ms
60.gif
3865 ms
2023.png
4071 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
66 ms
ad_status.js
75 ms
2022.png
4177 ms
1992.png
4637 ms
2020.png
4828 ms
2015.png
4706 ms
2009.png
4382 ms
2023.jpg
651 ms
2022.jpg
1079 ms
beauty_clock_logo.png
221 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
63 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
72 ms
1940.png
4547 ms
1908.png
5232 ms
160314_e576993661672fce0daa7b59609939c6
4979 ms
1984.png
5005 ms
1955.png
5073 ms
1796.png
5652 ms
1838.png
4993 ms
1948.png
4990 ms
2005.png
5006 ms
1812.png
5291 ms
160314_8f8be2e103d7ec11fca09cfd21f3ec66
6073 ms
160314_f959a751d3f8a93b8a5c4ffee871aa8f
5187 ms
160315_51b18d8353d428072a05d0eb16b7c592
6077 ms
i1.hk accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
i1.hk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
i1.hk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
ZH
N/A
BIG5
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I1.hk 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 I1.hk main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
i1.hk
Open Graph description is not detected on the main page of I 1. 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: