Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

bunit.dev

bUnit - a testing library for Blazor components | bUnit

Page Load Speed

726 ms in total

First Response

53 ms

Resources Loaded

534 ms

Page Rendered

139 ms

bunit.dev screenshot

About Website

Click here to check amazing BUnit content. Otherwise, check out these important facts you probably never knew about bunit.dev

bUnit is a unit testing library for Blazor Components. You can easily define components under test in C# or Razor syntax and verify outcome using semantic HTML diffing/comparison logic. You can intera...

Visit bunit.dev

Key Findings

We analyzed Bunit.dev page load time and found that the first response time was 53 ms and then it took 673 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

bunit.dev performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

95/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.117

85/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

bunit.dev

53 ms

docfx.min.css

18 ms

main.css

29 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

49 ms

bunit

161 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 39% of them (7 requests) were addressed to the original Bunit.dev, 39% (7 requests) were made to Img.shields.io and 17% (3 requests) were made to Avatars.githubusercontent.com. The less responsive or slowest element that took the longest time to load (412 ms) relates to the external source Img.shields.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.9 kB (28%)

Content Size

116.7 kB

After Optimization

83.8 kB

In fact, the total size of Bunit.dev main page is 116.7 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. Only 10% of websites need less resources to load. Images take 101.6 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.4 kB

  • Original 15.2 kB
  • After minification 14.2 kB
  • After compression 4.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 10.4 kB or 69% of the original size.

Image Optimization

-22%

Potential reduce by 22.5 kB

  • Original 101.6 kB
  • After minification 79.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. Obviously, BUnit needs image optimization as it can save up to 22.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

17

After Optimization

17

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BUnit. According to our analytics all requests are already optimized.

Accessibility Review

bunit.dev accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

bunit.dev best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

bunit.dev SEO score

89

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bunit.dev can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Bunit.dev 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 description is not detected on the main page of BUnit. 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: