Tools & Wizards About Us
onemex.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

onemex.com

墨西哥58同城-墨西哥58同城

Page Load Speed

16.4 sec in total

First Response

569 ms

Resources Loaded

15.6 sec

Page Rendered

246 ms

onemex.com screenshot

About Website

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

墨西哥58同城信息网致力于为全球华人提供最新、最快、最权威的墨西哥资讯,提供商业信息发布,行业资讯,招聘求职,二手交易,签证,旅游攻略等一站式服务。打造墨西哥华人生活服务第一网。

Visit onemex.com

Key Findings

We analyzed Onemex.com page load time and found that the first response time was 569 ms and then it took 15.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.

Performance Metrics

onemex.com performance score

0

Network Requests Diagram

www.onemex.com

569 ms

clear.png

4351 ms

fm.js

5348 ms

style_11_common.css

34 ms

common.js

17 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 45% of them (46 requests) were addressed to the original Onemex.com, 6% (6 requests) were made to Pagead2.googlesyndication.com and 6% (6 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (14.6 sec) relates to the external source 7xjv8c.com1.z0.glb.clouddn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 629.1 kB (33%)

Content Size

1.9 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onemex.com main page is 1.9 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 94.1 kB

  • Original 115.9 kB
  • After minification 115.1 kB
  • After compression 21.9 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 94.1 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 76.7 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Onemex images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 361.5 kB

  • Original 585.2 kB
  • After minification 500.4 kB
  • After compression 223.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 361.5 kB or 62% of the original size.

CSS Optimization

-78%

Potential reduce by 96.8 kB

  • Original 124.6 kB
  • After minification 119.9 kB
  • After compression 27.8 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. Onemex.com needs all CSS files to be minified and compressed as it can save up to 96.8 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (52%)

Requests Now

99

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.onemex.com

www.onemex.com

569 ms

clear.png

clear.png

4351 ms

fm.js

fm.js

5348 ms

style_11_common.css

style_11_common.css

34 ms

common.js

common.js

17 ms

portal.js

portal.js

46 ms

logging.js

logging.js

8 ms

focus.js

focus.js

19 ms

jquery-1.4.2.js

jquery-1.4.2.js

27 ms

style.css

style.css

68 ms

common2013.css

common2013.css

24 ms

index2014.css

index2014.css

30 ms

embed.js

embed.js

154 ms

converter-widget

converter-widget

181 ms

adsbygoogle.js

adsbygoogle.js

6 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

44 ms

ping.js

ping.js

730 ms

discuz_tips.js

discuz_tips.js

736 ms

ef2463eac5495860a186d37dfb5d5af9.jpg

ef2463eac5495860a186d37dfb5d5af9.jpg

8972 ms

16665445.asp

16665445.asp

1152 ms

50129c60584d5d2b5b4d8aed0b6a0284.jpg

50129c60584d5d2b5b4d8aed0b6a0284.jpg

14603 ms

xin163kbg.gif

xin163kbg.gif

137 ms

button.gif

button.gif

136 ms

nvbing5_bkdhksft.png

nvbing5_bkdhksft.png

136 ms

sidebar_wx.png

sidebar_wx.png

132 ms

qrcode.jpg

qrcode.jpg

137 ms

ad1.png

ad1.png

265 ms

onemex001.png

onemex001.png

220 ms

hotel-onemex.png

hotel-onemex.png

276 ms

cbfc0f9bc7144a32a68ea7f4e3e23748.jpg

cbfc0f9bc7144a32a68ea7f4e3e23748.jpg

271 ms

nophoto.gif

nophoto.gif

273 ms

viajeschinamexico.png

viajeschinamexico.png

296 ms

jiankonganzhuang.gif

jiankonganzhuang.gif

350 ms

guanggaowei.gif

guanggaowei.gif

331 ms

xinshengminlinliangtan.gif

xinshengminlinliangtan.gif

405 ms

wangzhansheji.gif

wangzhansheji.gif

351 ms

addh04_onemex.jpg

addh04_onemex.jpg

406 ms

default_0.jpg

default_0.jpg

535 ms

jin01.gif

jin01.gif

536 ms

jin02.gif

jin02.gif

537 ms

jin03.gif

jin03.gif

552 ms

jin04.gif

jin04.gif

553 ms

jin05.gif

jin05.gif

667 ms

hm.js

hm.js

987 ms

topnav_bg.png

topnav_bg.png

628 ms

mintip.gif

mintip.gif

627 ms

n5_gzwm.png

n5_gzwm.png

628 ms

logo.png

logo.png

628 ms

index2013_7_sp.gif

index2013_7_sp.gif

630 ms

index2013_7_sp.gif

index2013_7_sp.gif

726 ms

weather.aspx

weather.aspx

7821 ms

legacywidget-legacy-editable

legacywidget-legacy-editable

120 ms

01_avatar_middle.jpg

01_avatar_middle.jpg

405 ms

noavatar_middle.gif

noavatar_middle.gif

374 ms

searchbox.html

searchbox.html

399 ms

us.png

us.png

90 ms

cn.png

cn.png

169 ms

mx.png

mx.png

171 ms

px.png

px.png

268 ms

noavatar_middle.gif

noavatar_middle.gif

136 ms

ca-pub-5179302686514562.js

ca-pub-5179302686514562.js

71 ms

zrt_lookup.html

zrt_lookup.html

66 ms

show_ads_impl.js

show_ads_impl.js

67 ms

index2014_jobbtn.gif

index2014_jobbtn.gif

250 ms

js

js

1143 ms

common2013_sp.gif

common2013_sp.gif

189 ms

ads

ads

168 ms

osd.js

osd.js

18 ms

ads

ads

234 ms

Mjk1ODgwODc=.js

Mjk1ODgwODc=.js

332 ms

h.js

h.js

1229 ms

m_js_controller.js

m_js_controller.js

24 ms

abg.js

abg.js

38 ms

favicon

favicon

68 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

70 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

55 ms

s

s

44 ms

x_button_blue2.png

x_button_blue2.png

40 ms

favicon

favicon

79 ms

6be9c8fc3fc760ec78f75a8a0e2d36b5f5662ce2.css

6be9c8fc3fc760ec78f75a8a0e2d36b5f5662ce2.css

78 ms

5fc8859a0efa6426c14e3bc4acfe7d446e3baa72.css

5fc8859a0efa6426c14e3bc4acfe7d446e3baa72.css

79 ms

7e6bb600141a762e5ef0bb5f8c7c6a8c9516c1b8.css

7e6bb600141a762e5ef0bb5f8c7c6a8c9516c1b8.css

80 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

3 ms

hm.gif

hm.gif

359 ms

d59400a9e3fb1de83d0ecf952eef4e894acabc26.png

d59400a9e3fb1de83d0ecf952eef4e894acabc26.png

29 ms

go.asp

go.asp

1053 ms

widget.css

widget.css

3250 ms

1.css

1.css

3003 ms

scrolltop.png

scrolltop.png

135 ms

activeview

activeview

13 ms

profile.json

profile.json

1115 ms

hm.js

hm.js

646 ms

tp-weixin-qr.jpg

tp-weixin-qr.jpg

4549 ms

hm.gif

hm.gif

323 ms

blank.gif

blank.gif

2571 ms

weather.js

weather.js

681 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1694 ms

select.gif

select.gif

730 ms

fog.png

fog.png

1197 ms

cloud.png

cloud.png

835 ms

brain.png

brain.png

1650 ms

hm.gif

hm.gif

323 ms

SEO Factors

onemex.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onemex.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Onemex.com main page’s claimed encoding is gbk. 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

onemex.com

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