Tools & Wizards About Us
wymm.in screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wymm.in

Steam & Gas Boiler,,Hot Water Boiler,Gas Fired Boiler China

Page Load Speed

7.8 sec in total

First Response

720 ms

Resources Loaded

6.7 sec

Page Rendered

320 ms

wymm.in screenshot

About Website

Click here to check amazing Wymm content. Otherwise, check out these important facts you probably never knew about wymm.in

Wymm - Matchmaking done right

Visit wymm.in

Key Findings

We analyzed Wymm.in page load time and found that the first response time was 720 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

wymm.in performance score

0

Network Requests Diagram

wymm.in

720 ms

www.wymm.in

1637 ms

fontface.css

1560 ms

style.css

683 ms

header_footer_main.css

681 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 71% of them (44 requests) were addressed to the original Wymm.in, 5% (3 requests) were made to and 5% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Wymm.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (53%)

Content Size

1.9 MB

After Optimization

906.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wymm.in 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. 50% of websites need less resources to load. Javascripts take 859.5 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 14.2 kB

  • Original 19.2 kB
  • After minification 17.5 kB
  • After compression 5.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 14.2 kB or 74% of the original size.

Image Optimization

-9%

Potential reduce by 39.3 kB

  • Original 414.5 kB
  • After minification 375.2 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. Wymm images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 616.7 kB

  • Original 859.5 kB
  • After minification 714.2 kB
  • After compression 242.9 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 616.7 kB or 72% of the original size.

CSS Optimization

-55%

Potential reduce by 344.1 kB

  • Original 627.5 kB
  • After minification 608.3 kB
  • After compression 283.4 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. Wymm.in needs all CSS files to be minified and compressed as it can save up to 344.1 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (54%)

Requests Now

54

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wymm.in

wymm.in

720 ms

www.wymm.in

www.wymm.in

1637 ms

fontface.css

fontface.css

1560 ms

style.css

style.css

683 ms

header_footer_main.css

header_footer_main.css

681 ms

wymm-static.css

wymm-static.css

679 ms

646DFD17%25%25fbc_button.style.css

646DFD17%25%25fbc_button.style.css

458 ms

F9B03014%25%25fbc_button1.style.css

F9B03014%25%25fbc_button1.style.css

466 ms

jquery.js

jquery.js

2275 ms

jquery.browser.js

jquery.browser.js

695 ms

wymme_main.js

wymme_main.js

899 ms

interface.js

interface.js

903 ms

json2.js

json2.js

909 ms

component_handler.js

component_handler.js

926 ms

Ping.cmp.js

Ping.cmp.js

1891 ms

all.js

all.js

271 ms

FBCButton.cmp.js

FBCButton.cmp.js

1131 ms

SignIn.cmp.js

SignIn.cmp.js

1136 ms

FBCButton1.cmp.js

FBCButton1.cmp.js

1157 ms

responsive.css

responsive.css

1144 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

1809 ms

main.js

main.js

1170 ms

smoothPageScroll1.min.js

smoothPageScroll1.min.js

2047 ms

smoothPageScroll2.min.js

smoothPageScroll2.min.js

2128 ms

smoothPageScroll3.min.js

smoothPageScroll3.min.js

1559 ms

smoothPageScroll.min.js

smoothPageScroll.min.js

1784 ms

full_slider.js

full_slider.js

1898 ms

scroll_bottom_to_top1.js

scroll_bottom_to_top1.js

2007 ms

app-launch.jpg

app-launch.jpg

454 ms

facebook.png

facebook.png

235 ms

twitter.png

twitter.png

233 ms

Download-our-Android-App.png

Download-our-Android-App.png

230 ms

facebook_login.png

facebook_login.png

2250 ms

about_yourself.png

about_yourself.png

234 ms

we_match_you.png

we_match_you.png

455 ms

messaging_center.png

messaging_center.png

458 ms

third_slide_bg_logo.png

third_slide_bg_logo.png

461 ms

techstory.png

techstory.png

462 ms

we-are-the-city.png

we-are-the-city.png

674 ms

arrow.png

arrow.png

683 ms

logo.png

logo.png

668 ms

header_facebook.jpg

header_facebook.jpg

670 ms

love_heading.png

love_heading.png

676 ms

live_happily.png

live_happily.png

884 ms

analytics.js

analytics.js

80 ms

180 ms

dwED2QHAum4

dwED2QHAum4

94 ms

image1.jpg

image1.jpg

1242 ms

71r7AAAAAFUGac5AAA=

71r7AAAAAFUGac5AAA=

25 ms

yd7X4hdtZrsbdMxdmu7iotmQlFbU7bDOLcj4uLYaKTnJeliQ0ZePvRhT3xhAsYfHDBfEhbA7xI2YB0kHMBeS7iAU0j0AXfxAyNPBn283rInOr06gQHojxVDMNgrRmC4UozBaK6YgPFMMQWTqWIGpoXiAMwUW8rEB87EVQYAAAFUGac3AAA=

yd7X4hdtZrsbdMxdmu7iotmQlFbU7bDOLcj4uLYaKTnJeliQ0ZePvRhT3xhAsYfHDBfEhbA7xI2YB0kHMBeS7iAU0j0AXfxAyNPBn283rInOr06gQHojxVDMNgrRmC4UozBaK6YgPFMMQWTqWIGpoXiAMwUW8rEB87EVQYAAAFUGac3AAA=

24 ms

RcHuf0A+v9DwgAAAVQZpzgAAA==

RcHuf0A+v9DwgAAAVQZpzgAAA==

23 ms

xd_arbiter.php

xd_arbiter.php

234 ms

xd_arbiter.php

xd_arbiter.php

445 ms

collect

collect

20 ms

collect

collect

61 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

26 ms

www-embed-player.js

www-embed-player.js

49 ms

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

42 ms

ad_status.js

ad_status.js

46 ms

xd_arbiter.php

xd_arbiter.php

186 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

37 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

40 ms

SEO Factors

wymm.in SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wymm.in 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 Wymm.in 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.

Social Sharing Optimization

wymm.in

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