Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

bleene.com

Ben Lee - Sydney Based Artist & Graphic Designer • Bleene • Digital Portfolio

Page Load Speed

15 sec in total

First Response

546 ms

Resources Loaded

14.3 sec

Page Rendered

91 ms

About Website

Click here to check amazing Bleene content for Australia. Otherwise, check out these important facts you probably never knew about bleene.com

Online portfolio of Ben Lee, a Sydney based graphic artist & designer with expertise in print & digital advertising, Photoshop, Illustrator & Indesign

Visit bleene.com

Key Findings

We analyzed Bleene.com page load time and found that the first response time was 546 ms and then it took 14.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

bleene.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.8 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

bleene.com

546 ms

creative

590 ms

11025 ms

wp-emoji-release.min.js

383 ms

style.min.css

638 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 85% of them (28 requests) were addressed to the original Bleene.com, 9% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (11 sec) belongs to the original domain Bleene.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.4 kB (34%)

Content Size

387.5 kB

After Optimization

255.1 kB

In fact, the total size of Bleene.com main page is 387.5 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 178.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 57.6 kB

  • Original 67.8 kB
  • After minification 61.8 kB
  • After compression 10.2 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 57.6 kB or 85% of the original size.

JavaScript Optimization

-20%

Potential reduce by 36.3 kB

  • Original 178.1 kB
  • After minification 178.1 kB
  • After compression 141.9 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 36.3 kB or 20% of the original size.

CSS Optimization

-27%

Potential reduce by 38.6 kB

  • Original 141.6 kB
  • After minification 140.8 kB
  • After compression 103.0 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. Bleene.com needs all CSS files to be minified and compressed as it can save up to 38.6 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (88%)

Requests Now

24

After Optimization

3

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

Accessibility Review

bleene.com accessibility score

86

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

<frame> or <iframe> elements do not have a title

Best Practices

bleene.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

SEO Factors

bleene.com SEO score

92

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 doesn't use 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 Bleene.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 Bleene.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 Bleene. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: