Tools & Wizards About Us
whosms.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

whosms.com

Whosms.com - Short Text Messages - Funny SMS , Love SMS , Friendship SMS and Much More

Page Load Speed

3.7 sec in total

First Response

134 ms

Resources Loaded

3.3 sec

Page Rendered

206 ms

whosms.com screenshot

About Website

Click here to check amazing Whosms content for Pakistan. Otherwise, check out these important facts you probably never knew about whosms.com

We have many categorized Short Messages for mobile messaging. You can send those messages to your friends and family. We have many categories like , funny , friendship , love and many more.

Visit whosms.com

Key Findings

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

Performance Metrics

whosms.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

whosms.com

134 ms

Style.css

430 ms

WebResource.axd

70 ms

ScriptResource.axd

78 ms

ScriptResource.axd

88 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 20% of them (17 requests) were addressed to the original Whosms.com, 19% (16 requests) were made to Apis.google.com and 13% (11 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.3 kB (25%)

Content Size

638.1 kB

After Optimization

479.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whosms.com main page is 638.1 kB. 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. Javascripts take 505.7 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 94.8 kB

  • Original 108.1 kB
  • After minification 81.4 kB
  • After compression 13.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 26.8 kB, which is 25% 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 94.8 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 641 B

  • Original 19.2 kB
  • After minification 18.6 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. Whosms images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 61.0 kB

  • Original 505.7 kB
  • After minification 505.7 kB
  • After compression 444.7 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 61.0 kB or 12% of the original size.

CSS Optimization

-37%

Potential reduce by 1.9 kB

  • Original 5.1 kB
  • After minification 5.1 kB
  • After compression 3.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. Whosms.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (55%)

Requests Now

55

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whosms.com

whosms.com

134 ms

Style.css

Style.css

430 ms

WebResource.axd

WebResource.axd

70 ms

ScriptResource.axd

ScriptResource.axd

78 ms

ScriptResource.axd

ScriptResource.axd

88 ms

show_ads.js

show_ads.js

91 ms

jquery.js

jquery.js

38 ms

i.gif

i.gif

18 ms

Permalink.png

Permalink.png

70 ms

logo.jpg

logo.jpg

157 ms

bg_top_black.jpg

bg_top_black.jpg

62 ms

nav_separator.png

nav_separator.png

61 ms

bg_top_green.jpg

bg_top_green.jpg

61 ms

adsbygoogle.js

adsbygoogle.js

137 ms

nav_green.jpg

nav_green.jpg

65 ms

sms_icon.png

sms_icon.png

135 ms

nav_black.jpg

nav_black.jpg

140 ms

s11.g

s11.g

11 ms

like.php

like.php

336 ms

ratingStarEmpty.png

ratingStarEmpty.png

128 ms

StandardBtn.png

StandardBtn.png

292 ms

like.php

like.php

284 ms

like.php

like.php

306 ms

like.php

like.php

322 ms

like.php

like.php

296 ms

like.php

like.php

367 ms

like.php

like.php

405 ms

like.php

like.php

521 ms

like.php

like.php

527 ms

like.php

like.php

541 ms

widgets.js

widgets.js

90 ms

plusone.js

plusone.js

34 ms

Event.htm

Event.htm

95 ms

all.js

all.js

16 ms

all.js

all.js

55 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

43 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

42 ms

fastbutton

fastbutton

37 ms

fastbutton

fastbutton

42 ms

fastbutton

fastbutton

36 ms

fastbutton

fastbutton

40 ms

fastbutton

fastbutton

35 ms

fastbutton

fastbutton

36 ms

fastbutton

fastbutton

30 ms

fastbutton

fastbutton

29 ms

fastbutton

fastbutton

28 ms

fastbutton

fastbutton

162 ms

fastbutton

fastbutton

160 ms

14th-feb.jpg

14th-feb.jpg

171 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

194 ms

show_ads_impl.js

show_ads_impl.js

394 ms

postmessageRelay

postmessageRelay

114 ms

developers.google.com

developers.google.com

1241 ms

developers.google.com

developers.google.com

1268 ms

developers.google.com

developers.google.com

1412 ms

developers.google.com

developers.google.com

1937 ms

developers.google.com

developers.google.com

1167 ms

developers.google.com

developers.google.com

2318 ms

developers.google.com

developers.google.com

1657 ms

w9py8-RGams.js

w9py8-RGams.js

61 ms

FEppCFCt76d.png

FEppCFCt76d.png

61 ms

80 ms

developers.google.com

developers.google.com

2017 ms

developers.google.com

developers.google.com

2419 ms

developers.google.com

developers.google.com

2225 ms

settings

settings

98 ms

developers.google.com

developers.google.com

2099 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

17 ms

rpc:shindig_random.js

rpc:shindig_random.js

9 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

23 ms

embeds

embeds

36 ms

embeds

embeds

86 ms

embeds

embeds

142 ms

embeds

embeds

143 ms

embeds

embeds

143 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

74 ms

zrt_lookup.html

zrt_lookup.html

37 ms

ads

ads

41 ms

ads

ads

82 ms

ads

ads

42 ms

ads

ads

73 ms

ads

ads

63 ms

ads

ads

31 ms

Accessibility Review

whosms.com accessibility score

67

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

whosms.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

whosms.com SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

Social Sharing Optimization

whosms.com

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