Tools & Wizards About Us
henghengtoy.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

henghengtoy.com

henghengtoy.com

Page Load Speed

11.5 sec in total

First Response

1.9 sec

Resources Loaded

9.3 sec

Page Rendered

261 ms

henghengtoy.com screenshot

About Website

Visit henghengtoy.com now to see the best up-to-date Henghengtoy content and also check out these interesting facts you probably never knew about henghengtoy.com

จําหน่าย ขายกันดั้ม โมเดลกันดั้ม Model Gundam พลาสติกโมเดล โมเดลรถยนต์ โมเดลเครื่องบิน โมเดลมอเตอร์ไซด์ โมเดลรถจักรยานยนต์ ของสะสมที่เกี่ยวกับ Gundam ที่ ร้าน Heng Heng Toy ชลบุรี

Visit henghengtoy.com

Key Findings

We analyzed Henghengtoy.com page load time and found that the first response time was 1.9 sec and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

henghengtoy.com performance score

0

Network Requests Diagram

henghengtoy.com

1883 ms

ga.js

8 ms

mainstyle.js

516 ms

thumbnail170.css

771 ms

jquery-lastest.min.js

1036 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 87% of them (93 requests) were addressed to the original Henghengtoy.com, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Upic.me. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Toyzcool.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 809.4 kB (60%)

Content Size

1.3 MB

After Optimization

535.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Henghengtoy.com main page is 1.3 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. 45% of websites need less resources to load. Javascripts take 480.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 241.3 kB

  • Original 287.2 kB
  • After minification 274.2 kB
  • After compression 46.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 241.3 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 6.6 kB

  • Original 348.8 kB
  • After minification 342.3 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. Henghengtoy images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 356.9 kB

  • Original 480.2 kB
  • After minification 358.1 kB
  • After compression 123.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 356.9 kB or 74% of the original size.

CSS Optimization

-89%

Potential reduce by 204.6 kB

  • Original 228.8 kB
  • After minification 180.1 kB
  • After compression 24.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. Henghengtoy.com needs all CSS files to be minified and compressed as it can save up to 204.6 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (69%)

Requests Now

105

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Henghengtoy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

henghengtoy.com

henghengtoy.com

1883 ms

ga.js

ga.js

8 ms

mainstyle.js

mainstyle.js

516 ms

thumbnail170.css

thumbnail170.css

771 ms

jquery-lastest.min.js

jquery-lastest.min.js

1036 ms

jquery.tinyTips.js

jquery.tinyTips.js

528 ms

tinyTips.css

tinyTips.css

527 ms

jquery.MetaData.js

jquery.MetaData.js

772 ms

jquery.rating.js

jquery.rating.js

772 ms

jquery.rating.css

jquery.rating.css

772 ms

slideimg.css

slideimg.css

1018 ms

ssz.css

ssz.css

1033 ms

slideimg.css

slideimg.css

1032 ms

mainstyle.css

mainstyle.css

1033 ms

template.js

template.js

1282 ms

ui.all.css

ui.all.css

1272 ms

effects.core.js

effects.core.js

1290 ms

effects.scale.js

effects.scale.js

1291 ms

ui.core.js

ui.core.js

1290 ms

ui.draggable.js

ui.draggable.js

1286 ms

ui.dialog.js

ui.dialog.js

1528 ms

jquery.bgiframe.js

jquery.bgiframe.js

1536 ms

demos.css

demos.css

1553 ms

__utm.gif

__utm.gif

15 ms

wz_tooltip.js

wz_tooltip.js

1310 ms

slideimg.js

slideimg.js

1043 ms

mootools.js

mootools.js

1046 ms

WebResource.axd

WebResource.axd

1031 ms

WebResource.axd

WebResource.axd

1037 ms

ui.base.css

ui.base.css

260 ms

ui.theme.css

ui.theme.css

260 ms

en.png

en.png

409 ms

banner.gif

banner.gif

4488 ms

3XMGHJ23FEC0V294201160.gif

3XMGHJ23FEC0V294201160.gif

2324 ms

banner.gif

banner.gif

6337 ms

rx783_620x285.jpg

rx783_620x285.jpg

455 ms

gaiacolor.jpg

gaiacolor.jpg

531 ms

bttn_pop_info.png

bttn_pop_info.png

260 ms

bttn_pop_addtocart.png

bttn_pop_addtocart.png

261 ms

bttn_pop_ask.png

bttn_pop_ask.png

450 ms

bttn_chat_off.png

bttn_chat_off.png

456 ms

arrow_orange.gif

arrow_orange.gif

510 ms

trust_logo.gif

trust_logo.gif

512 ms

ssz_smalllogo.gif

ssz_smalllogo.gif

512 ms

tmplt_12.gif

tmplt_12.gif

512 ms

flag_th.gif

flag_th.gif

705 ms

flag_uk.gif

flag_uk.gif

711 ms

bttn_search_yellow.gif

bttn_search_yellow.gif

765 ms

tmplt_29.gif

tmplt_29.gif

766 ms

tmplt_40.gif

tmplt_40.gif

767 ms

tmplt_42.gif

tmplt_42.gif

767 ms

arrow_black.gif

arrow_black.gif

960 ms

img_bullet.gif

img_bullet.gif

967 ms

line_vertical.gif

line_vertical.gif

1021 ms

arrow_menu.gif

arrow_menu.gif

1022 ms

tmplt_46.gif

tmplt_46.gif

1024 ms

tmplt_48.gif

tmplt_48.gif

1022 ms

line_vertical2.gif

line_vertical2.gif

1220 ms

tmplt_50.gif

tmplt_50.gif

1222 ms

tmplt_34.gif

tmplt_34.gif

2719 ms

tmplt_37.gif

tmplt_37.gif

1820 ms

tmplt_39.gif

tmplt_39.gif

2715 ms

bttn_track.gif

bttn_track.gif

1778 ms

icon_link.gif

icon_link.gif

1475 ms

icon_cart.gif

icon_cart.gif

1476 ms

topic_home.gif

topic_home.gif

1888 ms

tmplt_16.gif

tmplt_16.gif

1747 ms

tmplt_19.gif

tmplt_19.gif

2002 ms

0.gif

0.gif

4027 ms

icon_email.gif

icon_email.gif

1889 ms

icon_phone.gif

icon_phone.gif

1948 ms

ui.core.css

ui.core.css

2005 ms

ui.resizable.css

ui.resizable.css

2080 ms

ui.accordion.css

ui.accordion.css

2145 ms

ui.dialog.css

ui.dialog.css

2259 ms

ui.slider.css

ui.slider.css

2271 ms

ui.tabs.css

ui.tabs.css

2265 ms

ui.datepicker.css

ui.datepicker.css

2266 ms

ui.progressbar.css

ui.progressbar.css

2463 ms

icon_mobile.gif

icon_mobile.gif

2471 ms

blink.gif

blink.gif

3217 ms

loading.htm

loading.htm

257 ms

popup_pay.png

popup_pay.png

521 ms

dialog_comment.png

dialog_comment.png

1070 ms

dialog_comment2.png

dialog_comment2.png

1070 ms

cart_float_1.png

cart_float_1.png

1058 ms

bar_top.gif

bar_top.gif

754 ms

bar_top.gif

bar_top.gif

970 ms

tmplt_41.gif

tmplt_41.gif

1014 ms

tmplt_26.gif

tmplt_26.gif

1235 ms

dash_line_horizontal.gif

dash_line_horizontal.gif

1269 ms

bttn_brown.gif

bttn_brown.gif

1228 ms

tmplt_17.gif

tmplt_17.gif

1272 ms

all.js

all.js

43 ms

dash_line.gif

dash_line.gif

1241 ms

bg_bottom.gif

bg_bottom.gif

1290 ms

53 ms

tmplt_08.gif

tmplt_08.gif

1346 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

23 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

34 ms

like.php

like.php

119 ms

indicator_circle_ball.gif

indicator_circle_ball.gif

1305 ms

VYSWNx3-H66.js

VYSWNx3-H66.js

36 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

22 ms

rounded-white.png

rounded-white.png

263 ms

zoomout.cur

zoomout.cur

262 ms

loader.white.gif

loader.white.gif

261 ms

SEO Factors

henghengtoy.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-874

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Henghengtoy.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 Henghengtoy.com main page’s claimed encoding is windows-874. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

henghengtoy.com

Open Graph description is not detected on the main page of Henghengtoy. 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: