22.3 sec in total
3 sec
18.4 sec
830 ms
Click here to check amazing Williamcheung content. Otherwise, check out these important facts you probably never knew about williamcheung.net
Reviews, Recommendations, Tips, Videos
Visit williamcheung.netWe analyzed Williamcheung.net page load time and found that the first response time was 3 sec and then it took 19.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
williamcheung.net performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value2.5 s
90/100
25%
Value1.4 s
100/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value2.3 s
99/100
10%
3023 ms
270 ms
160 ms
164 ms
160 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 82% of them (106 requests) were addressed to the original Williamcheung.net, 3% (4 requests) were made to Pagead2.googlesyndication.com and 2% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (12.8 sec) belongs to the original domain Williamcheung.net.
Page size can be reduced by 868.4 kB (32%)
2.7 MB
1.8 MB
In fact, the total size of Williamcheung.net main page is 2.7 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. 60% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 118.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 118.0 kB or 87% of the original size.
Potential reduce by 98.2 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. Williamcheung images are well optimized though.
Potential reduce by 370.0 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 370.0 kB or 66% of the original size.
Potential reduce by 282.2 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. Williamcheung.net needs all CSS files to be minified and compressed as it can save up to 282.2 kB or 83% of the original size.
Number of requests can be reduced by 67 (53%)
127
60
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Williamcheung. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.williamcheung.net
3023 ms
style.css
270 ms
wpinstagram.css
160 ms
jquery.fancybox-1.3.4.min.css
164 ms
style.css
160 ms
nextgen_gallery_related_images.css
169 ms
font-awesome.css
390 ms
wpss-search-suggest.css
317 ms
jquery.js
556 ms
jquery-migrate.min.js
326 ms
jquery.easing-1.3.pack.js
425 ms
jquery.cycle.all.js
629 ms
jquery.fancybox-1.3.4.pack.js
475 ms
jquery.mousewheel-3.0.4.pack.js
483 ms
ajax.js
545 ms
persist.js
658 ms
store.js
636 ms
ngg_store.js
643 ms
jquery.jj_ngg_shuffle.js
700 ms
lightbox_context.js
713 ms
video-js.css
787 ms
tube.css
791 ms
video.js
955 ms
script.js
814 ms
widgets.css
854 ms
nextgen_basic_thumbnails.css
875 ms
trigger_buttons.css
941 ms
shutter.css
945 ms
style.css
968 ms
nggallery.css
1016 ms
swfobject.js
1035 ms
brand
16 ms
widget.js
65 ms
show_ads.js
6 ms
brand
45 ms
suggest.min.js
804 ms
wpss-search-suggest.js
821 ms
common.js
821 ms
nextgen_basic_thumbnails.js
826 ms
shutter.js
905 ms
nextgen_shutter.js
923 ms
ga.js
25 ms
__utm.gif
37 ms
Bottom_texture.jpg
11699 ms
Middle_texture.png
300 ms
header.png
434 ms
header.jpg
11713 ms
get_flash_player.gif
18 ms
facebook.png
189 ms
linkedin.png
187 ms
twitter.png
184 ms
youtube.png
200 ms
google+.jpg
201 ms
tumblr.png
187 ms
digg.png
374 ms
DrawSomething-e1335312496857.png
370 ms
instagram-.png
11705 ms
thumbs_img_0433.png
516 ms
thumbs_photo-23-04-2013-21-44-32.jpg
11704 ms
thumbs_photo-12-09-2012-12-28-43.png
11702 ms
thumbs_dsc_0061.jpg
11927 ms
thumbs_img_0005-800x600.jpg
11931 ms
thumbs_img_1243-800x600.jpg
11844 ms
thumbs_photo-03-02-2014-11-31-21.png
11920 ms
thumbs_photo-03-02-2014-11-31-32.png
11924 ms
thumbs_photo-03-02-2014-11-32-37.png
11846 ms
thumbs_photo-03-02-2014-11-32-46.png
12076 ms
icon_biggrin.gif
12013 ms
thumbs_photo-14-05-2013-22-11-11.png
12078 ms
thumbs_photo-14-05-2013-22-11-19.png
12158 ms
thumbs_photo-14-05-2013-22-11-26.png
12164 ms
thumbs_photo-14-05-2013-22-11-31.png
12168 ms
thumbs_photo-14-05-2013-22-11-38.png
12311 ms
thumbs_photo-07-05-2013-00-50-23.png
12323 ms
thumbs_photo-07-05-2013-00-50-30.png
12325 ms
thumbs_photo-10-05-2013-01-02-58.png
12390 ms
thumbs_photo-11-05-2013-00-24-03.png
12437 ms
thumbs_photo-14-05-2013-22-02-51.png
12465 ms
thumbs_photo-14-05-2013-22-02-43.png
12545 ms
thumbs_photo-14-05-2013-21-47-46.png
12556 ms
thumbs_photo-14-05-2013-22-02-30.png
12474 ms
google_custom_search_watermark.gif
54 ms
ca-pub-3068798144659742.js
111 ms
zrt_lookup.html
49 ms
show_ads_impl.js
53 ms
thumbs_screenshot_2013-05-04-01-47-35.png
12471 ms
thumbs_screenshot_2013-05-04-01-47-41.png
12505 ms
thumbs_screenshot_2013-05-04-01-47-49.png
12527 ms
thumbs_screenshot_2013-05-04-01-52-30.png
12542 ms
ads
350 ms
osd.js
28 ms
QnVAitwYZz0
177 ms
7AksBqYgXfw
191 ms
ASO_zypdnsQ
156 ms
thumbs_screenshot_2013-05-04-01-52-41.png
12530 ms
ads
284 ms
thumbs_photo-02-05-2013-12-42-12.png
12427 ms
thumbs_photo-02-05-2013-12-41-27.png
12430 ms
www-embed-player-vfl8xM8me.css
62 ms
www-embed-player.js
91 ms
thumbs_photo-02-05-2013-12-41-21.png
12395 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
52 ms
ad_status.js
11224 ms
Photo-02-05-2013-12-31-10-576x1024.png
12848 ms
Photo-02-05-2013-12-36-43-576x1024.png
12679 ms
abg.js
11186 ms
thumbs_photo-30-04-2013-21-49-59.png
1247 ms
thumbs_photo-30-04-2013-21-50-12.png
1168 ms
thumbs_photo-30-04-2013-21-50-18.png
1173 ms
thumbs_photo-30-04-2013-21-51-46.png
1217 ms
thumbs_photo-30-04-2013-21-51-50.png
1314 ms
media-recorder-mac.png
1336 ms
nav.png
1231 ms
menuitem.png
1187 ms
menuseparator.png
1262 ms
sheet_s.png
1308 ms
sheet_h.png
1336 ms
sheet_v.png
1322 ms
post_s.png
1267 ms
post_h.png
1277 ms
post_v.png
1234 ms
post_c.png
1255 ms
postbullets.png
1314 ms
blockheader.png
1178 ms
blockcontent_s.png
1174 ms
blockcontent_h.png
1188 ms
blockcontent_v.png
1153 ms
rssicon.png
1137 ms
content_js2.php5
273 ms
williamcheung.net 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
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.
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
williamcheung.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
williamcheung.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Williamcheung.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Williamcheung.net 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.
williamcheung.net
Open Graph data is detected on the main page of Williamcheung. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: