13.2 sec in total
364 ms
12.2 sec
709 ms
Click here to check amazing Add 2 Trolley content for Hong Kong. Otherwise, check out these important facts you probably never knew about add2trolley.com
Search on topics your interested. Read great personalised news.
Visit add2trolley.comWe analyzed Add2trolley.com page load time and found that the first response time was 364 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
add2trolley.com performance score
364 ms
441 ms
4509 ms
284 ms
169 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 90% of them (176 requests) were addressed to the original Add2trolley.com, 3% (5 requests) were made to Apis.google.com and 2% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Add2trolley.com.
Page size can be reduced by 936.1 kB (44%)
2.1 MB
1.2 MB
In fact, the total size of Add2trolley.com main page is 2.1 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 426.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. This page needs HTML code to be minified as it can gain 230.8 kB, which is 51% 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 426.3 kB or 94% of the original size.
Potential reduce by 86.0 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. Add 2 Trolley images are well optimized though.
Potential reduce by 265.6 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 265.6 kB or 68% of the original size.
Potential reduce by 158.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. Add2trolley.com needs all CSS files to be minified and compressed as it can save up to 158.2 kB or 82% of the original size.
Number of requests can be reduced by 42 (22%)
191
149
The browser has sent 191 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Add 2 Trolley. 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 11 to 1 for CSS and as a result speed up the page load time.
add2trolley.com
364 ms
wp
441 ms
4509 ms
styles.css
284 ms
default.css
169 ms
jquery.jscrollpane.css
147 ms
plusone.js
96 ms
jquery.min.js
392 ms
core.js
217 ms
shortcodes.js
239 ms
jquery.template.js
532 ms
fitvids.js
288 ms
IE8.js
53 ms
style.css
308 ms
3682 ms
responsive.css
357 ms
jquery.sidr.dark.css
379 ms
jquery.js
640 ms
jquery-migrate.min.js
450 ms
account.admin.wpg.js
465 ms
merchant.admin.wpg.js
521 ms
jquery.public.wpg.js
545 ms
core.min.js
594 ms
widget.min.js
700 ms
tabs.min.js
624 ms
jquery.template.js
735 ms
jquery.tipTip.min.js
701 ms
js
32 ms
jquery.sidr.min.js
534 ms
shortcodes.css
1254 ms
retina.css
520 ms
bootstrap.css
509 ms
ui.totop.css
534 ms
jquery.contentcarousel.js
95 ms
jquery.slides.min.js
86 ms
jquery.scroller.js
74 ms
cb=gapi.loaded_0
56 ms
wp-emoji-release.min.js
168 ms
jquery.mobilemenu.js
130 ms
comment-reply.min.js
217 ms
jquery.easing.1.3.js
121 ms
blank.gif
213 ms
timthumb.php
267 ms
P8-Lite-box1.jpg
270 ms
P8-Lite-box2.jpg
848 ms
P8-Lite-box3.jpg
337 ms
P8-Lite-box4.jpg
336 ms
P8-Lite-box5.jpg
850 ms
P8-Lite-box6.jpg
838 ms
timthumb.php
841 ms
timthumb.php
842 ms
timthumb.php
843 ms
timthumb.php
845 ms
timthumb.php
846 ms
timthumb.php
850 ms
timthumb.php
849 ms
timthumb.php
852 ms
timthumb.php
853 ms
timthumb.php
915 ms
timthumb.php
913 ms
timthumb.php
854 ms
timthumb.php
855 ms
timthumb.php
913 ms
timthumb.php
912 ms
timthumb.php
912 ms
timthumb.php
928 ms
timthumb.php
1162 ms
timthumb.php
1113 ms
timthumb.php
1111 ms
timthumb.php
1111 ms
timthumb.php
1223 ms
timthumb.php
1109 ms
timthumb.php
1239 ms
timthumb.php
1315 ms
timthumb.php
1316 ms
timthumb.php
1315 ms
all.js
282 ms
timthumb.php
1407 ms
widgets.js
13 ms
fastbutton
147 ms
cb=gapi.loaded_0
63 ms
cb=gapi.loaded_1
64 ms
fontawesome-webfont.woff
1331 ms
timthumb.php
1111 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
571 ms
timthumb.php
1215 ms
timthumb.php
1143 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
90 ms
timthumb.php
658 ms
timthumb.php
694 ms
timthumb.php
857 ms
timthumb.php
850 ms
timthumb.php
851 ms
timthumb.php
846 ms
timthumb.php
853 ms
timthumb.php
980 ms
timthumb.php
974 ms
timthumb.php
928 ms
timthumb.php
987 ms
timthumb.php
1123 ms
timthumb.php
1003 ms
timthumb.php
1046 ms
89 ms
timthumb.php
1111 ms
xd_arbiter.php
221 ms
xd_arbiter.php
428 ms
timthumb.php
1205 ms
timthumb.php
1067 ms
timthumb.php
1135 ms
timthumb.php
1138 ms
timthumb.php
1300 ms
timthumb.php
1198 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
18 ms
like.php
66 ms
xd_arbiter.php
204 ms
rU2ubZ6l1Q5.js
483 ms
LVx-xkvaJ0b.png
548 ms
jot
87 ms
timthumb.php
1041 ms
timthumb.php
1083 ms
timthumb.php
1076 ms
timthumb.php
1246 ms
timthumb.php
1088 ms
timthumb.php
1063 ms
timthumb.php
1113 ms
timthumb.php
1132 ms
timthumb.php
1170 ms
timthumb.php
1139 ms
timthumb.php
1057 ms
timthumb.php
1130 ms
timthumb.php
1159 ms
timthumb.php
1166 ms
timthumb.php
1124 ms
timthumb.php
1125 ms
timthumb.php
1135 ms
timthumb.php
1008 ms
timthumb.php
1098 ms
timthumb.php
1276 ms
timthumb.php
1136 ms
timthumb.php
1187 ms
timthumb.php
1195 ms
timthumb.php
1245 ms
timthumb.php
1133 ms
timthumb.php
1146 ms
timthumb.php
1167 ms
timthumb.php
1253 ms
timthumb.php
1228 ms
timthumb.php
1157 ms
timthumb.php
1200 ms
timthumb.php
1162 ms
timthumb.php
1277 ms
timthumb.php
1154 ms
timthumb.php
1170 ms
timthumb.php
1210 ms
timthumb.php
1346 ms
timthumb.php
1144 ms
timthumb.php
1258 ms
timthumb.php
1195 ms
timthumb.php
1361 ms
timthumb.php
1197 ms
timthumb.php
1149 ms
timthumb.php
1152 ms
timthumb.php
1161 ms
timthumb.php
1177 ms
timthumb.php
1286 ms
timthumb.php
1146 ms
timthumb.php
1137 ms
timthumb.php
1126 ms
timthumb.php
1168 ms
timthumb.php
1282 ms
timthumb.php
1163 ms
timthumb.php
1157 ms
timthumb.php
1211 ms
timthumb.php
1263 ms
timthumb.php
1074 ms
timthumb.php
1063 ms
timthumb.php
1073 ms
timthumb.php
1215 ms
timthumb.php
1099 ms
timthumb.php
1105 ms
timthumb.php
1099 ms
timthumb.php
1054 ms
timthumb.php
1067 ms
timthumb.php
1134 ms
visa_master.png
998 ms
ppcom.svg
1027 ms
header_bg_sm.png
1103 ms
add2trolley6.240x48.png
972 ms
spriteme2.png
946 ms
spriteme1.png
1022 ms
overlay_x.png
946 ms
discountmin.png
903 ms
arrows.png
868 ms
bg-footer.jpg
872 ms
twitter.png
969 ms
gotop.gif
867 ms
add2trolley.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Add2trolley.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 Add2trolley.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.
add2trolley.com
Open Graph data is detected on the main page of Add 2 Trolley. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: