Tools & Wizards About Us
whatsup.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whatsup.net

WhatsUp.net

Page Load Speed

2.1 sec in total

First Response

488 ms

Resources Loaded

1.5 sec

Page Rendered

160 ms

whatsup.net screenshot

About Website

Welcome to whatsup.net homepage info - get ready to check Whats Up best content for India right away, or after learning these important things about whatsup.net

Visit whatsup.net

Key Findings

We analyzed Whatsup.net page load time and found that the first response time was 488 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

whatsup.net performance score

0

Network Requests Diagram

whatsup.net

488 ms

ga.js

8 ms

comment.css

152 ms

ModalPopup.css

168 ms

MultiImage.css

147 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 92% of them (35 requests) were addressed to the original Whatsup.net, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Piwik.webcontrolcenter.com. The less responsive or slowest element that took the longest time to load (488 ms) belongs to the original domain Whatsup.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.7 kB (63%)

Content Size

138.7 kB

After Optimization

52.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatsup.net main page is 138.7 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. 20% of websites need less resources to load. Javascripts take 60.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 24.2 kB

  • Original 34.7 kB
  • After minification 31.1 kB
  • After compression 10.5 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 24.2 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.3 kB
  • After minification 2.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. Whats Up images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 28.3 kB

  • Original 60.6 kB
  • After minification 60.6 kB
  • After compression 32.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 28.3 kB or 47% of the original size.

CSS Optimization

-83%

Potential reduce by 34.2 kB

  • Original 41.1 kB
  • After minification 28.4 kB
  • After compression 6.9 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. Whatsup.net needs all CSS files to be minified and compressed as it can save up to 34.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (84%)

Requests Now

37

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatsup.net

whatsup.net

488 ms

ga.js

ga.js

8 ms

comment.css

comment.css

152 ms

ModalPopup.css

ModalPopup.css

168 ms

MultiImage.css

MultiImage.css

147 ms

PhotoForm.css

PhotoForm.css

153 ms

style.css

style.css

365 ms

widget.css

widget.css

218 ms

__utm.gif

__utm.gif

14 ms

WebResource.axd

WebResource.axd

231 ms

ScriptResource.axd

ScriptResource.axd

303 ms

ScriptResource.axd

ScriptResource.axd

245 ms

ScriptResource.axd

ScriptResource.axd

143 ms

ScriptResource.axd

ScriptResource.axd

157 ms

ScriptResource.axd

ScriptResource.axd

216 ms

ScriptResource.axd

ScriptResource.axd

297 ms

ScriptResource.axd

ScriptResource.axd

290 ms

ScriptResource.axd

ScriptResource.axd

299 ms

ScriptResource.axd

ScriptResource.axd

327 ms

wulogo_02.gif

wulogo_02.gif

328 ms

whatsuptitle_03.gif

whatsuptitle_03.gif

372 ms

st_events.gif

st_events.gif

382 ms

st_places.gif

st_places.gif

404 ms

st_near.gif

st_near.gif

393 ms

menu_home.gif

menu_home.gif

371 ms

menu_calendar.gif

menu_calendar.gif

397 ms

menu_addevent.gif

menu_addevent.gif

442 ms

menu_addplace.gif

menu_addplace.gif

451 ms

boxshadowUR.gif

boxshadowUR.gif

452 ms

nophoto.gif

nophoto.gif

466 ms

boxshadowLL.gif

boxshadowLL.gif

420 ms

boxshadowLR.gif

boxshadowLR.gif

422 ms

French-Quarter-Jacguard-P3.gif

French-Quarter-Jacguard-P3.gif

300 ms

date_add.png

date_add.png

193 ms

map_add.png

map_add.png

194 ms

map.png

map.png

213 ms

stripebg_13.gif

stripebg_13.gif

218 ms

piwik.js

piwik.js

353 ms

SEO Factors

whatsup.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatsup.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Whatsup.net main page’s claimed encoding is iso-8859-1. 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

whatsup.net

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