Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

Page Load Speed

2.1 sec in total

First Response

124 ms

Resources Loaded

1.5 sec

Page Rendered

451 ms

reportcard.supportbee.com screenshot

About Website

Click here to check amazing Reportcard Support Bee content for United States. Otherwise, check out these important facts you probably never knew about reportcard.supportbee.com

SupportBee launched on September 26th 2012. Find out what the team has been upto in the 12 months since the launch!

Visit reportcard.supportbee.com

Key Findings

We analyzed Reportcard.supportbee.com page load time and found that the first response time was 124 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

reportcard.supportbee.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

reportcard.supportbee.com

124 ms

reportcard.supportbee.com

217 ms

base_v2-datauri.css

143 ms

app_v2-datauri.css

126 ms

reportcard-datauri.css

326 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Reportcard.supportbee.com, 38% (15 requests) were made to Use.typekit.com and 26% (10 requests) were made to D1vijro2f92n44.cloudfront.net. The less responsive or slowest element that took the longest time to load (440 ms) relates to the external source Use.typekit.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 407.7 kB (42%)

Content Size

979.1 kB

After Optimization

571.5 kB

In fact, the total size of Reportcard.supportbee.com main page is 979.1 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. 40% of websites need less resources to load. Images take 439.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 37.7 kB

  • Original 44.2 kB
  • After minification 44.2 kB
  • After compression 6.5 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 37.7 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 17.5 kB

  • Original 439.1 kB
  • After minification 421.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. Reportcard Support Bee images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 182.4 kB

  • Original 259.1 kB
  • After minification 201.8 kB
  • After compression 76.6 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 182.4 kB or 70% of the original size.

CSS Optimization

-72%

Potential reduce by 170.1 kB

  • Original 236.8 kB
  • After minification 229.1 kB
  • After compression 66.8 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. Reportcard.supportbee.com needs all CSS files to be minified and compressed as it can save up to 170.1 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (42%)

Requests Now

24

After Optimization

14

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

Accessibility Review

reportcard.supportbee.com accessibility score

84

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

reportcard.supportbee.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

Page has valid source maps

SEO Factors

reportcard.supportbee.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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 Reportcard.supportbee.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 Reportcard.supportbee.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

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