Tools & Wizards About Us
pulse.ms screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

pulse.ms

Pulse - Project Management Software - All in One System

Page Load Speed

4.9 sec in total

First Response

500 ms

Resources Loaded

4 sec

Page Rendered

375 ms

pulse.ms screenshot

About Website

Click here to check amazing Pulse content. Otherwise, check out these important facts you probably never knew about pulse.ms

Manage more with Pulse! Project Management, Tasks, Finances, Timesheets, Document Management, Calendar, Resource Planner - All-In-One System

Visit pulse.ms

Key Findings

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

Performance Metrics

pulse.ms performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

36/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

pulse.ms

500 ms

www.pulsecollab.com

1032 ms

css2

29 ms

wpo-minify-header-7adb8c94.min.css

787 ms

wpo-minify-header-f5440c18.min.js

811 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pulse.ms, 83% (29 requests) were made to Pulsecollab.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Pulsecollab.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.1 kB (11%)

Content Size

989.4 kB

After Optimization

884.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pulse.ms main page is 989.4 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. 55% of websites need less resources to load. Images take 486.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 54.9 kB

  • Original 70.0 kB
  • After minification 61.7 kB
  • After compression 15.1 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 8.3 kB, which is 12% 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 54.9 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 4.1 kB

  • Original 486.2 kB
  • After minification 482.1 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. Pulse images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 17.1 kB

  • Original 320.2 kB
  • After minification 320.2 kB
  • After compression 303.1 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

-26%

Potential reduce by 29.0 kB

  • Original 113.0 kB
  • After minification 113.0 kB
  • After compression 84.0 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. Pulse.ms needs all CSS files to be minified and compressed as it can save up to 29.0 kB or 26% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pulse.ms

pulse.ms

500 ms

www.pulsecollab.com

www.pulsecollab.com

1032 ms

css2

css2

29 ms

wpo-minify-header-7adb8c94.min.css

wpo-minify-header-7adb8c94.min.css

787 ms

wpo-minify-header-f5440c18.min.js

wpo-minify-header-f5440c18.min.js

811 ms

ht-kb-frontend.min.js

ht-kb-frontend.min.js

407 ms

wpo-minify-footer-2e5757de.min.js

wpo-minify-footer-2e5757de.min.js

985 ms

api.js

api.js

33 ms

wpo-minify-footer-67371d13.min.js

wpo-minify-footer-67371d13.min.js

615 ms

gtm.js

gtm.js

129 ms

pulse_logo.svg

pulse_logo.svg

258 ms

loading.svg

loading.svg

257 ms

Upside-down-mountains-bg.svg

Upside-down-mountains-bg.svg

262 ms

pulse-ornamental-graphics-landing-page-01@2x.png

pulse-ornamental-graphics-landing-page-01@2x.png

257 ms

pulse-ornamental-graphic-landing-page-2@2x.png

pulse-ornamental-graphic-landing-page-2@2x.png

455 ms

Pulse-Support-Team-3-e1617670847743.png

Pulse-Support-Team-3-e1617670847743.png

1051 ms

pulse-ornamental-graphic-landing-page-3@2x.png

pulse-ornamental-graphic-landing-page-3@2x.png

453 ms

pulse-ornamental-graphic-landing-page-4@2x-1.png

pulse-ornamental-graphic-landing-page-4@2x-1.png

658 ms

features-grid.svg

features-grid.svg

525 ms

tools_logos_v2.svg

tools_logos_v2.svg

1824 ms

Rachael_Owens@2x-68x68-c-left.png

Rachael_Owens@2x-68x68-c-left.png

664 ms

David_Smith@2x-68x68-c-left.png

David_Smith@2x-68x68-c-left.png

653 ms

Umi_Zuko@2x-68x68-c-left.png

Umi_Zuko@2x-68x68-c-left.png

722 ms

pulse_logo_reversed.svg

pulse_logo_reversed.svg

851 ms

havas_logo.svg

havas_logo.svg

858 ms

vivendi_logo.svg

vivendi_logo.svg

859 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjp-Ek-_0ew.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjp-Ek-_0ew.woff

862 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZFhjp-Ek-_0ewmM.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZFhjp-Ek-_0ewmM.woff

995 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZBhjp-Ek-_0ewmM.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZBhjp-Ek-_0ewmM.woff

1004 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZxhjp-Ek-_0ewmM.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZxhjp-Ek-_0ewmM.woff

1004 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZNhjp-Ek-_0ewmM.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZNhjp-Ek-_0ewmM.woff

1059 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZthjp-Ek-_0ewmM.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZthjp-Ek-_0ewmM.woff

1193 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZJhjp-Ek-_0ewmM.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZJhjp-Ek-_0ewmM.woff

1193 ms

font

font

20 ms

recaptcha__en.js

recaptcha__en.js

36 ms

Accessibility Review

pulse.ms accessibility score

91

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

Image elements do not have [alt] attributes

Best Practices

pulse.ms best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pulse.ms SEO score

92

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

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

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 Pulse.ms 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 Pulse.ms 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

pulse.ms

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