10.9 sec in total
86 ms
5.9 sec
4.9 sec
Click here to check amazing Uncle Teh Peng content for Singapore. Otherwise, check out these important facts you probably never knew about uncletehpeng.com
Visit uncletehpeng.comWe analyzed Uncletehpeng.com page load time and found that the first response time was 86 ms and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
uncletehpeng.com performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value5.0 s
27/100
25%
Value2.2 s
99/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value3.4 s
93/100
10%
86 ms
225 ms
23 ms
50 ms
91 ms
Our browser made a total of 208 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Uncletehpeng.com, 10% (21 requests) were made to 3.bp.blogspot.com and 10% (20 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (4.9 sec) relates to the external source Synad3.nuffnang.com.sg.
Page size can be reduced by 578.7 kB (5%)
12.2 MB
11.7 MB
In fact, the total size of Uncletehpeng.com main page is 12.2 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 11.5 MB which makes up the majority of the site volume.
Potential reduce by 226.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 226.5 kB or 83% of the original size.
Potential reduce by 66.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. Uncle Teh Peng images are well optimized though.
Potential reduce by 233.5 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 233.5 kB or 62% of the original size.
Potential reduce by 51.9 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. Uncletehpeng.com needs all CSS files to be minified and compressed as it can save up to 51.9 kB or 72% of the original size.
Number of requests can be reduced by 66 (33%)
203
137
The browser has sent 203 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uncle Teh Peng. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
uncletehpeng.com
86 ms
www.uncletehpeng.com
225 ms
webfont.js
23 ms
3375562265-css_bundle_v2.css
50 ms
authorization.css
91 ms
plusone.js
76 ms
jquery.min.js
32 ms
jquery.flexslider-min.js
72 ms
engageya_blogger.js
76 ms
3226477086-widgets.js
40 ms
css
40 ms
image
206 ms
cb=gapi.loaded_0
187 ms
cb=gapi.loaded_1
185 ms
google_top_exp.js
185 ms
a3_1.jpg
460 ms
icon18_wrench_allbkg.png
163 ms
a2.jpg
165 ms
a15.jpg
163 ms
a16.jpg
164 ms
a9.jpg
161 ms
icon18_edit_allbkg.gif
153 ms
paging_dot.png
147 ms
sprk.1.0.2.js
147 ms
lb.js
551 ms
widgets.js
142 ms
285 ms
cb=gapi.loaded_2
72 ms
cb=gapi.loaded_3
70 ms
fastbutton
154 ms
fastbutton
151 ms
fastbutton
198 ms
stats
181 ms
a20.jpg
123 ms
a22.jpg
165 ms
a7.jpg
169 ms
a5.jpg
173 ms
a36.jpg
174 ms
a25.jpg
174 ms
IMG_2373.JPG
173 ms
a3.jpg
216 ms
a1.jpg
225 ms
a14.jpg
230 ms
a8.jpg
215 ms
a5.jpg
233 ms
a48.jpg
230 ms
a67.jpg
282 ms
a65.jpg
281 ms
a70.jpg
277 ms
a71.jpg
279 ms
a14.jpg
120 ms
a19.jpg
150 ms
a21.jpg
125 ms
a4.jpg
149 ms
a34.jpg
164 ms
a26.jpg
164 ms
a27.jpg
168 ms
a35.jpg
168 ms
a12.jpg
213 ms
a15.jpg
212 ms
a7.jpg
224 ms
a43.jpg
212 ms
a44.jpg
213 ms
a51.jpg
225 ms
a54.jpg
278 ms
a66.jpg
277 ms
share_buttons_20_3.png
113 ms
a33.jpg
121 ms
a28.jpg
145 ms
a38.jpg
162 ms
a2.jpg
156 ms
a9.jpg
144 ms
a10.jpg
166 ms
a42.jpg
167 ms
a49.jpg
209 ms
a56.jpg
206 ms
a53.jpg
219 ms
a61.jpg
221 ms
a62.jpg
217 ms
a69.jpg
219 ms
a12.jpg
287 ms
a17.jpg
117 ms
a18.jpg
155 ms
a23.jpg
153 ms
a6.jpg
164 ms
a8.jpg
162 ms
a24.jpg
162 ms
a11.jpg
161 ms
a29.jpg
218 ms
a32.jpg
244 ms
a31.jpg
220 ms
a37.jpg
204 ms
a4.jpg
220 ms
Screen%2BShot%2B2015-06-23%2Bat%2B8.47.06%2Bpm.png
218 ms
a40.jpg
270 ms
a50.jpg
281 ms
a55.jpg
270 ms
a58.jpg
269 ms
a52.jpg
268 ms
a60.jpg
282 ms
a64.jpg
328 ms
a7.jpg
449 ms
a6.jpg
447 ms
a4.jpg
474 ms
a5.jpg
398 ms
hen.png
328 ms
here.png
447 ms
Screenshot2014-05-27atPM074852.png
471 ms
STCommunitiesBiggerIcon1.gif
560 ms
done11.jpg
635 ms
a1_2.jpg
718 ms
done2.jpg
635 ms
DONE3.jpg
720 ms
done4.jpg
638 ms
done7.jpg
717 ms
DONE9.jpg
749 ms
e1.jpg
752 ms
ljpKc6CdXusL1cnGUSamX4kaQb-UsZVONjobs91YQtw.woff
103 ms
88x31.png
147 ms
likebox.php
335 ms
navbar.g
107 ms
blank.html
101 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
178 ms
getrecs.json
565 ms
getrecs.json
567 ms
getrecs.json
563 ms
cb=gapi.loaded_4
111 ms
postmessageRelay
177 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
65 ms
icons_gray.png
141 ms
platform:gapi.iframes.style.common.js
78 ms
combined.css
72 ms
smoothDivScroll.css
95 ms
stack_161235.js
207 ms
jquery.min.js
99 ms
arrows-black.png
136 ms
cb=gapi.loaded_0
93 ms
cb=gapi.loaded_1
76 ms
xZQOmYg4x3YaWkTJi1kErvesZW2xOQ-xsNqO47m55DA.woff
156 ms
cb=gapi.loaded_0
47 ms
cb=gapi.loaded_1
45 ms
fastbutton
109 ms
syndication
241 ms
283913480829014016
303 ms
3193398744-postmessagerelay.js
140 ms
rpc:shindig_random.js
87 ms
postmessageRelay
82 ms
ebiMDO3r-8l.css
149 ms
jGc-59L_9lo.css
167 ms
q68gy-v_YMF.js
202 ms
FJmpeSpHpjS.js
239 ms
0wM5s1Khldu.js
225 ms
1bNoFZUdlYZ.js
223 ms
cb=gapi.loaded_0
68 ms
cb=gapi.loaded_1
66 ms
analytics.js
62 ms
stackpile.api-6712054ce0.js
74 ms
12826266_963675387048441_118957577_n.jpg
221 ms
small_share_sprite.png
46 ms
play_small.png
34 ms
12826081_981426495244806_223283328_n.jpg
261 ms
10608001_916026178505026_268578860_n.jpg
340 ms
12328055_531358940378939_842421563_n.jpg
354 ms
12798040_1520873294881075_2050636748_n.jpg
381 ms
10725132_1107612772602493_1476875525_n.jpg
355 ms
12816795_475190112684739_114968984_n.jpg
378 ms
12063085_1675553172734121_1931303822_n.jpg
381 ms
12383521_185291455185408_608889077_n.jpg
378 ms
cb=gapi.loaded_0
20 ms
collect
23 ms
collect
66 ms
1
4851 ms
stackpile.api-6712054ce0.js
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
3 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
6 ms
10388184_666232323471569_883266575407757413_n.jpg
197 ms
10399433_660300197398115_6475862454690541844_n.jpg
223 ms
12744483_10153511980434952_1093037133559967991_n.jpg
238 ms
10308206_1579367572351092_1981251973247896403_n.jpg
251 ms
12250070_10153819268201694_8012453267778189881_n.jpg
287 ms
1385754_380239148773677_1935882997_n.jpg
265 ms
10906065_10204125910844431_1100453412676349618_n.jpg
266 ms
wL6VQj7Ab77.png
39 ms
s7jcwEQH7Sx.png
39 ms
cw4Jd_oS_normal.jpg
190 ms
4.bp.blogspot.com.a2_2_196040_3.jpg
118 ms
facebook-like.png
67 ms
2.bp.blogspot.com.me_2_179960_3.jpg
498 ms
1.bp.blogspot.com.a3_2_139470_3.jpg
482 ms
all.js
134 ms
2.bp.blogspot.com.IMG_5F2373_2_124578_3.jpg
486 ms
facebook-counter-bg.png
65 ms
facebook-counter-repeat.png
73 ms
2.bp.blogspot.com.a1_2_123993_3.jpg
291 ms
scontent.xx.fbcdn.net.12814489_993183987443066_803615376069052352_n.jpg_125740_3.jpg
347 ms
3.bp.blogspot.com.a9_2_163617_3.jpg
666 ms
scontent.xx.fbcdn.net.12525949_989723144455817_624959321_n.jpg_119529_3.jpg
348 ms
3.bp.blogspot.com.a2_2_166409_3.jpg
93 ms
2.bp.blogspot.com.a8_2_138830_3.jpg
464 ms
i4.ytimg.com.default_2_186814_3.jpg
475 ms
nr-885.min.js
31 ms
a53393d12f
46 ms
51 ms
xd_arbiter.php
76 ms
xd_arbiter.php
130 ms
I6-MnjEovm5.js
22 ms
pQrUxxo5oQp.js
22 ms
jot
27 ms
uncletehpeng.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
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.
uncletehpeng.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
uncletehpeng.com 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
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uncletehpeng.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Uncletehpeng.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.
uncletehpeng.com
Open Graph description is not detected on the main page of Uncle Teh Peng. 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: