4.8 sec in total
326 ms
4.1 sec
361 ms
Visit tommyooi.com now to see the best up-to-date Tommy Ooi content for Malaysia and also check out these interesting facts you probably never knew about tommyooi.com
Traveling Made Simple
Visit tommyooi.comWe analyzed Tommyooi.com page load time and found that the first response time was 326 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tommyooi.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value5.4 s
21/100
25%
Value6.3 s
41/100
10%
Value530 ms
55/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
326 ms
137 ms
168 ms
166 ms
165 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 15% of them (18 requests) were addressed to the original Tommyooi.com, 8% (10 requests) were made to Static.xx.fbcdn.net and 8% (10 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source S3-ap-southeast-1.amazonaws.com.
Page size can be reduced by 611.1 kB (40%)
1.5 MB
931.1 kB
In fact, the total size of Tommyooi.com main page is 1.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. 70% of websites need less resources to load. Images take 659.5 kB which makes up the majority of the site volume.
Potential reduce by 126.3 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 126.3 kB or 79% of the original size.
Potential reduce by 24.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. Tommy Ooi images are well optimized though.
Potential reduce by 262.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 262.8 kB or 54% of the original size.
Potential reduce by 197.5 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. Tommyooi.com needs all CSS files to be minified and compressed as it can save up to 197.5 kB or 83% of the original size.
Number of requests can be reduced by 54 (50%)
109
55
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tommy Ooi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.tommyooi.com
326 ms
wp-emoji-release.min.js
137 ms
ultimate-tables.css
168 ms
jquery.dataTables.css
166 ms
sb-instagram.css
165 ms
font-awesome.min.css
6 ms
css
62 ms
style.css
158 ms
font-awesome.min.css
165 ms
jetpack.css
212 ms
jquery.js
317 ms
jquery-migrate.min.js
242 ms
scripts.js
241 ms
adsbygoogle.js
17 ms
293452
204 ms
liveView.php
30 ms
jquery.dataTables.min.js
315 ms
photon.js
184 ms
sb-instagram.js
236 ms
devicepx-jetpack.js
60 ms
gprofiles.js
55 ms
wpgroho.js
312 ms
wp-embed.min.js
312 ms
e-201609.js
5 ms
analytics.js
35 ms
IMG_6005.jpg
149 ms
Travel.jpg
228 ms
1-DTBK-Festive-22-Kitchen-Bar.jpg
173 ms
Krakow.jpg
608 ms
IMG_5409.jpg
23 ms
IMG_1186.jpg
147 ms
11900027_718828914928686_3941113452500137433_n.png
23 ms
DSC_5964.jpg
228 ms
DSC_6664.jpg
176 ms
DSC_5898.jpg
21 ms
DSC_6476.jpg
221 ms
DSC_6392.jpg
22 ms
1.png
222 ms
193.jpg
540 ms
my_en_freeseat.jpg
18 ms
lb.js
162 ms
mobile.js
151 ms
collect
30 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
67 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
81 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
96 ms
fontawesome-webfont.woff
464 ms
fontawesome-webfont.woff
6 ms
JsMapper.ashx
24 ms
hc_searchbox.css
7 ms
poweredby_hotelscombined.png
20 ms
ss.js
607 ms
liveView.php
89 ms
collect
84 ms
1
597 ms
loader.png
330 ms
acj
319 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
27 ms
sdk.js
312 ms
lr.js
311 ms
996145163
218 ms
recent
327 ms
hovercard.css
143 ms
services.css
145 ms
hc_pixel.gif
129 ms
hc_icon_calendar.png
61 ms
liveVideo.php
118 ms
dvtp_src.js
57 ms
g.gif
27 ms
1
579 ms
137 ms
xd_arbiter.php
33 ms
xd_arbiter.php
61 ms
11386424_1183752234984942_1502856715_a.jpg
283 ms
lightintegration.js
9 ms
beacons
31 ms
1
575 ms
12716944_549368651893176_777758872_n.jpg
250 ms
12749835_989928667723645_1557958930_n.jpg
281 ms
11349251_197669377262335_11051670_n.jpg
280 ms
12728545_1288245071189689_543818797_n.jpg
281 ms
12728411_514366562079306_596034168_n.jpg
282 ms
12729421_233257517013166_900386947_n.jpg
281 ms
12747748_1690008734604024_216674838_n.jpg
295 ms
12716565_996096217151148_143135963_n.jpg
347 ms
12783411_1688319008124032_1175029204_n.jpg
345 ms
2925.jpg
58 ms
pc_56ce746242fa2_lb_135391.jpeg
1819 ms
pc_style.css
499 ms
css
21 ms
quant.js
5 ms
log_placement.js
530 ms
pc-label.png
1020 ms
pc-view-icon.png
899 ms
pixel;r=1050014322;a=p-KAmbFRXjwDgHE;labels=synad_my;fpan=1;fpa=P0-1997778483-1456790098114;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456790098114;tzo=-180;ref=;url=http%3A%2F%2Fwww.tommyooi.com%2F;ogl=type.website%2Ctitle.Tommy%20Ooi%20Travel%20Guide%2Cdescription.Traveling%20Made%20Simple%2Curl.http%3A%2F%2Fwww%252Etommyooi%252Ecom%2F%2Csite_name.Tommy%20Ooi%20Travel%20Guide%2Cimage.https%3A%2F%2Fs0%252Ewp%252Ecom%2Fi%2Fblank%252Ejpg%2Clocale.en_US
6 ms
1153981.gif
31 ms
1153991.png
44 ms
nuffnang_footer_2.png
29 ms
gradientHorizontal.png
512 ms
bcplnphK3jNGowiu9YNSfA.ttf
43 ms
page.php
332 ms
o_zjiOVHPPW.css
51 ms
_rx8naC75Dy.js
66 ms
t-KLv3gqZy0.js
88 ms
uLtKx7ldlvR.js
88 ms
10615453_10152652752629770_2132802506777805957_n.jpg
51 ms
11760184_10153477374529770_351473994686190116_n.jpg
53 ms
11885218_10203302436361528_4284236888361986046_n.jpg
63 ms
12654316_10207524604867523_443075525792077247_n.jpg
70 ms
12806186_10205525064556077_962182357101416471_n.jpg
72 ms
12729076_10153884923417440_1763504794199638683_n.jpg
72 ms
1929945_1189682117727487_2448933964996720798_n.jpg
70 ms
12745617_10153805720668654_558129473756043540_n.jpg
71 ms
wL6VQj7Ab77.png
33 ms
CSXXCvknpgK.png
34 ms
R9a_DtVRZgv.js
8 ms
cUDgRFxaoIk.js
9 ms
0JBr1QHp8Gi.js
9 ms
kDOzhTr2W91.js
15 ms
tommyooi.com 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
Image elements do not have [alt] attributes
tommyooi.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
tommyooi.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tommyooi.com 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 Tommyooi.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.
tommyooi.com
Open Graph data is detected on the main page of Tommy Ooi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: