Tools & Wizards About Us
pulsior.io screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pulsior.io

Pulsior, digital receipts for brick and mortar businesses

Page Load Speed

7.4 sec in total

First Response

2.6 sec

Resources Loaded

4.3 sec

Page Rendered

460 ms

pulsior.io screenshot

About Website

Click here to check amazing Pulsior content. Otherwise, check out these important facts you probably never knew about pulsior.io

A powerful communication tool, enabling you to engage and communicate with your customers like never before

Visit pulsior.io

Key Findings

We analyzed Pulsior.io page load time and found that the first response time was 2.6 sec and then it took 4.8 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

pulsior.io performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

82/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

pulsior.io

2641 ms

autoptimize_8e0f04841e748c2b92a0baed59b39c21.css

793 ms

autoptimize_single_198dc5acc34bbb39feb6f8f398322df3.css

28 ms

autoptimize_single_5e37b8de1f21a9d4a442efae2a7550cb.css

25 ms

autoptimize_single_1e51b984a8756f6f41b113145ec0deac.css

499 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 51% of them (25 requests) were addressed to the original Pulsior.io, 31% (15 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Pulsior.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.4 kB (20%)

Content Size

1.1 MB

After Optimization

840.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pulsior.io main page is 1.1 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. Images take 678.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 73.2 kB

  • Original 84.5 kB
  • After minification 84.5 kB
  • After compression 11.4 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 73.2 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 33.5 kB

  • Original 678.6 kB
  • After minification 645.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. Pulsior images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 520 B

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

CSS Optimization

-96%

Potential reduce by 104.2 kB

  • Original 108.3 kB
  • After minification 4.1 kB
  • After compression 4.1 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. Pulsior.io needs all CSS files to be minified and compressed as it can save up to 104.2 kB or 96% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (41%)

Requests Now

32

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pulsior.io

pulsior.io

2641 ms

autoptimize_8e0f04841e748c2b92a0baed59b39c21.css

autoptimize_8e0f04841e748c2b92a0baed59b39c21.css

793 ms

autoptimize_single_198dc5acc34bbb39feb6f8f398322df3.css

autoptimize_single_198dc5acc34bbb39feb6f8f398322df3.css

28 ms

autoptimize_single_5e37b8de1f21a9d4a442efae2a7550cb.css

autoptimize_single_5e37b8de1f21a9d4a442efae2a7550cb.css

25 ms

autoptimize_single_1e51b984a8756f6f41b113145ec0deac.css

autoptimize_single_1e51b984a8756f6f41b113145ec0deac.css

499 ms

autoptimize_single_7647f37d102ea4760e524416d6bf5e12.css

autoptimize_single_7647f37d102ea4760e524416d6bf5e12.css

456 ms

jquery.js

jquery.js

604 ms

email-decode.min.js

email-decode.min.js

27 ms

lazysizes.min.js

lazysizes.min.js

36 ms

autoptimize_dcffac0d5827930583d695b5eaba15ed.js

autoptimize_dcffac0d5827930583d695b5eaba15ed.js

56 ms

gtm.js

gtm.js

171 ms

webfont.js

webfont.js

82 ms

ready-2.png

ready-2.png

813 ms

quot.png

quot.png

86 ms

iconfinder_Check_1063906-2.png

iconfinder_Check_1063906-2.png

504 ms

asdfghj.png

asdfghj.png

85 ms

fa-brands-400.woff

fa-brands-400.woff

663 ms

css

css

40 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

90 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

117 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

162 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

198 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

220 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

219 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

199 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

219 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

196 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

219 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

221 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

221 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

222 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

249 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

248 ms

cropped-Group.png

cropped-Group.png

22 ms

2-ocl4smhr3xwranikjiqlsiicboewtnif5d3mi6lvcw.png

2-ocl4smhr3xwranikjiqlsiicboewtnif5d3mi6lvcw.png

20 ms

1-ocl4smhr3xwranikjiqlsiicboewtnif5d3mi6lvcw.png

1-ocl4smhr3xwranikjiqlsiicboewtnif5d3mi6lvcw.png

636 ms

sadfdsd-300x300.png

sadfdsd-300x300.png

24 ms

1234567890--ocl4smhr3xygofjfjqrzdu0dh7rinbfyxtl4l26q68.png

1234567890--ocl4smhr3xygofjfjqrzdu0dh7rinbfyxtl4l26q68.png

26 ms

analytics.js

analytics.js

127 ms

destination

destination

80 ms

3-ocl4smhr3xwranikjiqlsiicboewtnif5d3mi6lvcw.png

3-ocl4smhr3xwranikjiqlsiicboewtnif5d3mi6lvcw.png

20 ms

1234567890--ocl4smhr3xygofjfjqrzdu0dh7rinbfyxtl4l26q68.png

1234567890--ocl4smhr3xygofjfjqrzdu0dh7rinbfyxtl4l26q68.png

94 ms

4-ocl4smhr3xwranikjiqlsiicboewtnif5d3mi6lvcw.png

4-ocl4smhr3xwranikjiqlsiicboewtnif5d3mi6lvcw.png

47 ms

qweqwe-300x300.png

qweqwe-300x300.png

80 ms

collect

collect

58 ms

cropped-Group.png

cropped-Group.png

24 ms

collect

collect

131 ms

js

js

74 ms

ga-audiences

ga-audiences

37 ms

Accessibility Review

pulsior.io accessibility score

96

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

Links do not have a discernible name

Best Practices

pulsior.io best practices score

75

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

SEO Factors

pulsior.io SEO score

100

Search Engine Optimization Advices

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 Pulsior.io 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 Pulsior.io 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

pulsior.io

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