Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

happybob.app

Happy Bob App turns diabetes data into rewarding experiences

Page Load Speed

3 sec in total

First Response

80 ms

Resources Loaded

2 sec

Page Rendered

937 ms

happybob.app screenshot

About Website

Click here to check amazing Happy Bob content. Otherwise, check out these important facts you probably never knew about happybob.app

Happy Bob uses real-time CGM data and turns diabetes management into more rewarding, playful moments that help keeping blood sugar more stable.

Visit happybob.app

Key Findings

We analyzed Happybob.app page load time and found that the first response time was 80 ms and then it took 2.9 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

happybob.app performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value6,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

happybob.app

80 ms

happybob.app

489 ms

uc.js

81 ms

js

161 ms

css2

80 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 40% of them (12 requests) were addressed to the original Happybob.app, 17% (5 requests) were made to Cdnjs.cloudflare.com and 10% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source S3.eu-central-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.9 kB (19%)

Content Size

652.2 kB

After Optimization

525.3 kB

In fact, the total size of Happybob.app main page is 652.2 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. 60% of websites need less resources to load. Images take 460.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 108.9 kB

  • Original 129.3 kB
  • After minification 127.0 kB
  • After compression 20.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 108.9 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 8.6 kB

  • Original 460.2 kB
  • After minification 451.6 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. Happy Bob images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 9.4 kB

  • Original 49.4 kB
  • After minification 49.4 kB
  • After compression 40.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 9.4 kB or 19% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 13.3 kB
  • After minification 13.3 kB
  • After compression 13.3 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. Happybob.app has all CSS files already compressed.

Requests Breakdown

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

Requests Now

24

After Optimization

11

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

Accessibility Review

happybob.app accessibility score

91

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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 IDs are not unique

Best Practices

happybob.app 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

SEO Factors

happybob.app 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 Happybob.app 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 Happybob.app 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

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