3.2 sec in total
57 ms
2.8 sec
405 ms
Visit whoknown.com now to see the best up-to-date Whoknown content for Thailand and also check out these interesting facts you probably never knew about whoknown.com
Technology | Electronics | Telecom | Social Network | Trip | Food & Drinks | Health & Sports | Lifestyle
Visit whoknown.comWe analyzed Whoknown.com page load time and found that the first response time was 57 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
whoknown.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.3 s
10/100
25%
Value7.3 s
29/100
10%
Value2,100 ms
7/100
30%
Value0.01
100/100
15%
Value19.8 s
2/100
10%
57 ms
119 ms
47 ms
42 ms
50 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Whoknown.com, 11% (18 requests) were made to 1.bp.blogspot.com and 11% (18 requests) were made to 3.bp.blogspot.com. The less responsive or slowest element that took the longest time to load (952 ms) relates to the external source Tracker.stats.in.th.
Page size can be reduced by 838.1 kB (25%)
3.4 MB
2.5 MB
In fact, the total size of Whoknown.com main page is 3.4 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. 85% 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.2 MB which makes up the majority of the site volume.
Potential reduce by 212.6 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 212.6 kB or 77% of the original size.
Potential reduce by 109.5 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. Whoknown images are well optimized though.
Potential reduce by 498.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 498.2 kB or 58% of the original size.
Potential reduce by 17.7 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. Whoknown.com needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 61% of the original size.
Number of requests can be reduced by 56 (38%)
147
91
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whoknown. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
whoknown.com
57 ms
www.whoknown.com
119 ms
css
47 ms
font-awesome.css
42 ms
1535467126-widget_css_2_bundle.css
50 ms
css
56 ms
css
75 ms
css
75 ms
jquery.min.js
37 ms
adsbygoogle.js
29 ms
jsapi
30 ms
t13n
40 ms
brand
37 ms
tracker.php
952 ms
addthis_widget.js
25 ms
3226477086-widgets.js
31 ms
plusone.js
129 ms
brand
291 ms
t13n
220 ms
all.js
123 ms
header-dots.png
123 ms
soc-icon-fb.png
180 ms
soc-icon-p.png
179 ms
icon18_wrench_allbkg.png
177 ms
Screenshot_2016-02-10-12-15-08.jpg
339 ms
summary
483 ms
Screenshot_2016-02-10-12-10-46.jpg
399 ms
gmail.PNG
439 ms
turn%2Bnoti.PNG
148 ms
turn%2Bnoti3.PNG
295 ms
Screenshot_2016-02-04-22-52-51.jpg
241 ms
turn%2Bnoti4.png
295 ms
line%2Bpc2.PNG
242 ms
Screenshot_2016-01-26-08-30-53.jpg
235 ms
replace%2Bfont%2Bpowerpoint%2B2.PNG
240 ms
Line-2-logo.jpg
313 ms
lin0.png
312 ms
lineeeee-horz.jpg
314 ms
back_to_top_button.png
312 ms
zen2.PNG
347 ms
zen2.PNG
419 ms
Screenshot_2016-02-10-12-02-42.jpg
449 ms
Screenshot_2016-02-10-12-02-59.jpg
448 ms
google%2Bsecurity%2Bcheck2.PNG
447 ms
google%2Bsecurity%2Bcheck2.PNG
448 ms
Capture.PNG
449 ms
layout%2Bwindows%2Bfolder%2B1.PNG
448 ms
layout%2Bwindows%2Bfolder%2B1.PNG
478 ms
layout%2Bwindows%2Bfolder%2B4.png
478 ms
replace%2Bfont%2Bpowerpoint3.PNG
297 ms
bot.JPG
233 ms
bot.JPG
297 ms
kbank.JPG
237 ms
Truemove-H.PNG
291 ms
SC20130228-141139.png
232 ms
Adblock+plus.PNG
311 ms
no-image.png
210 ms
1.JPG
578 ms
1.JPG
608 ms
3.JPG
638 ms
4.JPG
638 ms
Screenshot_2016-02-10-12-41-45.jpg
634 ms
Screenshot_2016-02-10-12-02-45.jpg
640 ms
Screenshot_2016-02-10-12-02-47.jpg
638 ms
Screenshot_2016-02-10-12-02-52.jpg
703 ms
google%2Bsecurity%2Bcheck%2B2.PNG
706 ms
layout%2Bwindows%2Bfolder%2B0.PNG
706 ms
layout%2Bwindows%2Bfolder%2B3.png
703 ms
layout%2Bwindows%2Bfolder%2B5.PNG
703 ms
line%2Bpc1.PNG
235 ms
line%2Bpc1.PNG
315 ms
SC20120608-191609.png
231 ms
12603672121260367405l.jpg
234 ms
soc-icon-instagram.png
142 ms
icon-search.png
142 ms
5.JPG
293 ms
Screenshot_2016-02-10-12-15-14.jpg
392 ms
Untitled.png
430 ms
google.PNG
430 ms
layout%2Bwindows%2Bfolder%2B2.png
436 ms
turn%2Bnoti2.png
227 ms
turn%2Bnoti2.png
227 ms
Screenshot_2016-01-26-08-30-41.jpg
233 ms
replace%2Bfont%2Bpowerpoint1.png
288 ms
replace%2Bfont%2Bpowerpoint1.png
306 ms
2015-03-26%2B10.36.20.jpg
233 ms
logo_truemove.gif
303 ms
ca-pub-6049241800812996.js
298 ms
zrt_lookup.html
326 ms
show_ads_impl.js
219 ms
228 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
153 ms
dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf
193 ms
MEz38VLIFL-t46JUtkIEgH4UHu-c0cTZKOwO_f6u1Os.ttf
215 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
215 ms
rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf
213 ms
fontawesome-webfont.woff
86 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
213 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
218 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
216 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
218 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
217 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
217 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
217 ms
xd_arbiter.php
130 ms
xd_arbiter.php
214 ms
ads
426 ms
osd.js
103 ms
12 ms
transliteration.css
3 ms
transliteration.I.js
10 ms
43 ms
analytics.js
42 ms
google_custom_search_watermark.gif
65 ms
js15.js
16 ms
inputtools.js
35 ms
2099262.php
22 ms
collect
72 ms
cc_235.js
17 ms
378784852393342141
33 ms
abg.js
44 ms
m_js_controller.js
58 ms
googlelogo_color_112x36dp.png
53 ms
s
26 ms
x_button_blue2.png
25 ms
veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js
4 ms
tracker.js
823 ms
ti.js
98 ms
cb=gapi.loaded_0
76 ms
stats
68 ms
chart
106 ms
stats-flipper.png
104 ms
p
68 ms
cOuLsaCtKr44Yoacwqm_6l.js
65 ms
page.php
83 ms
activeview
16 ms
stat.gif
263 ms
SAb9vLtZAm_.css
28 ms
XCdv7aD40Gm.js
36 ms
tknZmeHjRao.js
58 ms
nw0sMxy_KfY.js
57 ms
v2
102 ms
10565113_430286640447202_8483169214187708508_n.png
52 ms
1014457_639341089502060_7352513930771147150_n.jpg
25 ms
11094690_693802830741732_2961570412702796826_n.jpg
26 ms
10375081_191381444574194_6848516031379883916_n.jpg
25 ms
1383617_1156114077738809_7615664467321798549_n.jpg
32 ms
12806145_975069719226059_4218262609488030044_n.jpg
32 ms
11752539_858691740890269_1983875814186686973_n.jpg
34 ms
10334474_1695213047417088_2959572781861245644_n.jpg
32 ms
1507039_1991559521068287_9050360307949843894_n.jpg
31 ms
wL6VQj7Ab77.png
20 ms
WTZ_Jhk-ooC.png
12 ms
dpx
19 ms
R9GKCzjAnbk.js
31 ms
AWWjhOengNF.js
29 ms
YnSasnyq68i.js
29 ms
kQf_jlUv-kX.js
34 ms
ca.png
167 ms
xrefid.xgi
4 ms
300lo.json
45 ms
sh.953eb77977227bfd253ee158.html
27 ms
ui
37 ms
pi.png
7 ms
layers.34f2ad207a6dc0c4eb95.js
8 ms
whoknown.com accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
whoknown.com 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
whoknown.com SEO score
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
TH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoknown.com can be misinterpreted by Google and other search engines. Our service has detected that Thai 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 Whoknown.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.
whoknown.com
Open Graph description is not detected on the main page of Whoknown. 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: