Tools & Wizards About Us
whatpulse.org screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

whatpulse.org

WhatPulse: Track and Analyze your Activity and Productivity

Page Load Speed

2.5 sec in total

First Response

90 ms

Resources Loaded

2.1 sec

Page Rendered

342 ms

whatpulse.org screenshot

About Website

Visit whatpulse.org now to see the best up-to-date What Pulse content for Vietnam and also check out these interesting facts you probably never knew about whatpulse.org

Track and analyze your keystrokes and mouse clicks with WhatPulse. Gain insights into your productivity and usage patterns.

Visit whatpulse.org

Key Findings

We analyzed Whatpulse.org page load time and found that the first response time was 90 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

whatpulse.org performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

40/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.487

17/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

whatpulse.org

90 ms

whatpulse.org

201 ms

script.tagged-events.outbound-links.js

58 ms

colorbox.css

120 ms

bootstrap.min.css

130 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 83% of them (35 requests) were addressed to the original Whatpulse.org, 10% (4 requests) were made to Chat.whatpulse.org and 5% (2 requests) were made to Embed.famewall.io. The less responsive or slowest element that took the longest time to load (979 ms) relates to the external source Embed.famewall.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 149.9 kB (9%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatpulse.org main page is 1.7 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 25.4 kB

  • Original 33.1 kB
  • After minification 33.1 kB
  • After compression 7.7 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 25.4 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 90.9 kB

  • Original 1.2 MB
  • After minification 1.1 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. What Pulse images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.8 kB

  • Original 417.1 kB
  • After minification 417.1 kB
  • After compression 410.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-24%

Potential reduce by 26.9 kB

  • Original 111.6 kB
  • After minification 89.0 kB
  • After compression 84.7 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. Whatpulse.org needs all CSS files to be minified and compressed as it can save up to 26.9 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (64%)

Requests Now

36

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Pulse. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whatpulse.org

whatpulse.org

90 ms

whatpulse.org

whatpulse.org

201 ms

script.tagged-events.outbound-links.js

script.tagged-events.outbound-links.js

58 ms

colorbox.css

colorbox.css

120 ms

bootstrap.min.css

bootstrap.min.css

130 ms

dashboard.css

dashboard.css

139 ms

all.min.css

all.min.css

146 ms

bootstrap-select.min.css

bootstrap-select.min.css

160 ms

dashboard-dark.css

dashboard-dark.css

124 ms

whatpulse.css

whatpulse.css

248 ms

whatpulse-dark.css

whatpulse-dark.css

232 ms

whatpulse-logo-solid-black.png

whatpulse-logo-solid-black.png

235 ms

whatpulse-logo-solid-white.png

whatpulse-logo-solid-white.png

235 ms

frame.js

frame.js

841 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

320 ms

jquery.nanoscroller.js

jquery.nanoscroller.js

332 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

347 ms

bootstrap.min.js

bootstrap.min.js

363 ms

froala_editor.js

froala_editor.js

359 ms

bootstrap-select.min.js

bootstrap-select.min.js

360 ms

date.js

date.js

382 ms

jquery.timezone.js

jquery.timezone.js

389 ms

whatpulse.dashboard.js

whatpulse.dashboard.js

785 ms

whatpulse.js

whatpulse.js

475 ms

whatpulse.chatwoot.init.js

whatpulse.chatwoot.init.js

476 ms

home-desk.png

home-desk.png

520 ms

light-keyboard-heatmap.png

light-keyboard-heatmap.png

492 ms

light-network-applications.png

light-network-applications.png

550 ms

light-mouse-heatmap.png

light-mouse-heatmap.png

610 ms

light-input-applications.png

light-input-applications.png

609 ms

light-input-history.png

light-input-history.png

608 ms

light-application-activity-1.png

light-application-activity-1.png

638 ms

spinner.gif

spinner.gif

660 ms

fa-brands-400.woff

fa-brands-400.woff

468 ms

fa-regular-400.woff

fa-regular-400.woff

423 ms

fa-light-300.woff

fa-light-300.woff

431 ms

fa-solid-900.woff

fa-solid-900.woff

459 ms

iframeResizer.min.js

iframeResizer.min.js

979 ms

sdk.js

sdk.js

44 ms

widget

widget

660 ms

widget-7e897bca48a2e67c1dd4.js

widget-7e897bca48a2e67c1dd4.js

47 ms

widget-8fd04777.css

widget-8fd04777.css

27 ms

Accessibility Review

whatpulse.org accessibility score

77

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

Best Practices

whatpulse.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

whatpulse.org SEO score

81

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Whatpulse.org 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 Whatpulse.org 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

whatpulse.org

Open Graph data is detected on the main page of What Pulse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: