Tools & Wizards About Us
helpful.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

helpful.com

A big ‘thank you’ to the Helpful community | by daniel debow | Medium

Page Load Speed

823 ms in total

First Response

156 ms

Resources Loaded

506 ms

Page Rendered

161 ms

helpful.com screenshot

About Website

Visit helpful.com now to see the best up-to-date Helpful content for United States and also check out these interesting facts you probably never knew about helpful.com

Three years ago Farhan, David and I started Helpful to build the next generation of enterprise mobile products using AI. We focused on hard problems in fast growing companies for which there was a…

Visit helpful.com

Key Findings

We analyzed Helpful.com page load time and found that the first response time was 156 ms and then it took 667 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

helpful.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value6,980 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

helpful.com

156 ms

a-big-thank-you-to-the-helpful-community-46ec9380d12b

64 ms

unbound.css

41 ms

manifest.a0175d6a.js

37 ms

54.bea2e5cf.js

90 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Helpful.com, 57% (31 requests) were made to Cdn-client.medium.com and 31% (17 requests) were made to Glyph.medium.com. The less responsive or slowest element that took the longest time to load (201 ms) relates to the external source Cdn-client.medium.com.

Page Optimization Overview & Recommendations

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

Content Size

739.0 kB

After Optimization

674.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 63.2 kB

  • Original 86.9 kB
  • After minification 86.9 kB
  • After compression 23.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 63.2 kB or 73% of the original size.

Image Optimization

-4%

Potential reduce by 310 B

  • Original 8.3 kB
  • After minification 8.0 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. Helpful images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 726 B

  • Original 642.7 kB
  • After minification 642.7 kB
  • After compression 642.0 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

-6%

Potential reduce by 60 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 960 B

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. Helpful.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

36

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

helpful.com

helpful.com

156 ms

a-big-thank-you-to-the-helpful-community-46ec9380d12b

a-big-thank-you-to-the-helpful-community-46ec9380d12b

64 ms

unbound.css

unbound.css

41 ms

manifest.a0175d6a.js

manifest.a0175d6a.js

37 ms

54.bea2e5cf.js

54.bea2e5cf.js

90 ms

main.159e328e.js

main.159e328e.js

131 ms

instrumentation.d9108df7.chunk.js

instrumentation.d9108df7.chunk.js

113 ms

reporting.ff22a7a5.chunk.js

reporting.ff22a7a5.chunk.js

113 ms

5049.d1ead72d.chunk.js

5049.d1ead72d.chunk.js

98 ms

4810.988332a1.chunk.js

4810.988332a1.chunk.js

113 ms

7407.1ade2c73.chunk.js

7407.1ade2c73.chunk.js

114 ms

382.a98f5384.chunk.js

382.a98f5384.chunk.js

123 ms

9148.3242ff58.chunk.js

9148.3242ff58.chunk.js

146 ms

9977.b539ef71.chunk.js

9977.b539ef71.chunk.js

135 ms

5025.ca06885a.chunk.js

5025.ca06885a.chunk.js

135 ms

5250.a2539c10.chunk.js

5250.a2539c10.chunk.js

134 ms

6349.02c5ee3e.chunk.js

6349.02c5ee3e.chunk.js

135 ms

3801.7d014b43.chunk.js

3801.7d014b43.chunk.js

146 ms

2648.746e1532.chunk.js

2648.746e1532.chunk.js

153 ms

8594.9eac1902.chunk.js

8594.9eac1902.chunk.js

165 ms

6003.d14e9f7d.chunk.js

6003.d14e9f7d.chunk.js

150 ms

6636.e588ac65.chunk.js

6636.e588ac65.chunk.js

160 ms

3735.3535ed24.chunk.js

3735.3535ed24.chunk.js

161 ms

4300.dc9e14c6.chunk.js

4300.dc9e14c6.chunk.js

166 ms

6546.be06c6f7.chunk.js

6546.be06c6f7.chunk.js

176 ms

6834.f2d3924e.chunk.js

6834.f2d3924e.chunk.js

175 ms

6858.454b4e14.chunk.js

6858.454b4e14.chunk.js

182 ms

2420.0330d157.chunk.js

2420.0330d157.chunk.js

188 ms

5832.97239afc.chunk.js

5832.97239afc.chunk.js

186 ms

8980.6c8ff2c1.chunk.js

8980.6c8ff2c1.chunk.js

182 ms

2859.a9a624d0.chunk.js

2859.a9a624d0.chunk.js

190 ms

6040.6ceb7f43.chunk.js

6040.6ceb7f43.chunk.js

197 ms

4391.3e417aeb.chunk.js

4391.3e417aeb.chunk.js

200 ms

PostPage.MainContent.1ad05aca.chunk.js

PostPage.MainContent.1ad05aca.chunk.js

201 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

78 ms

1*dmbNkD5D-u45r44go_cf0g.png

1*dmbNkD5D-u45r44go_cf0g.png

70 ms

0*17-V4VmuXCq4RHMs.jpg

0*17-V4VmuXCq4RHMs.jpg

86 ms

0*17-V4VmuXCq4RHMs.jpg

0*17-V4VmuXCq4RHMs.jpg

88 ms

sohne-400-normal.woff

sohne-400-normal.woff

32 ms

sohne-400-normal.woff

sohne-400-normal.woff

43 ms

sohne-500-normal.woff

sohne-500-normal.woff

44 ms

sohne-500-normal.woff

sohne-500-normal.woff

52 ms

sohne-300-normal.woff

sohne-300-normal.woff

44 ms

sohne-300-normal.woff

sohne-300-normal.woff

51 ms

sohne-700-normal.woff

sohne-700-normal.woff

68 ms

sohne-700-normal.woff

sohne-700-normal.woff

62 ms

source-serif-pro-400-normal.woff

source-serif-pro-400-normal.woff

35 ms

source-serif-pro-400-normal.woff

source-serif-pro-400-normal.woff

17 ms

source-serif-pro-700-normal.woff

source-serif-pro-700-normal.woff

21 ms

source-serif-pro-700-normal.woff

source-serif-pro-700-normal.woff

21 ms

source-serif-pro-400-italic.woff

source-serif-pro-400-italic.woff

35 ms

source-serif-pro-400-italic.woff

source-serif-pro-400-italic.woff

35 ms

source-serif-pro-700-italic.woff

source-serif-pro-700-italic.woff

50 ms

source-serif-pro-700-italic.woff

source-serif-pro-700-italic.woff

49 ms

Accessibility Review

helpful.com accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

helpful.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

helpful.com SEO score

99

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

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 Helpful.com 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 Helpful.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

helpful.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: