Tools & Wizards About Us
lbarr.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

lbarr.com

Melbourne based web designer and developer - Liam Barr

Page Load Speed

4.4 sec in total

First Response

768 ms

Resources Loaded

3.2 sec

Page Rendered

475 ms

lbarr.com screenshot

About Website

Welcome to lbarr.com homepage info - get ready to check L Barr best content right away, or after learning these important things about lbarr.com

Liam Barr is a Melbourne based web designer and developer with a focus on simplify the future. He builds site with a focus on simplicity and usability.

Visit lbarr.com

Key Findings

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

Performance Metrics

lbarr.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

lbarr.com

768 ms

c5b5e3973f54572788cd92556a7cb777.html

509 ms

8217d7b.js

433 ms

be2eb8f.js

57 ms

3cad222.js

498 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 94% of them (16 requests) were addressed to the original Lbarr.com, 6% (1 request) were made to Cdn.lightwidget.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Lbarr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.7 kB (31%)

Content Size

853.8 kB

After Optimization

592.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lbarr.com main page is 853.8 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. 20% of websites need less resources to load. Javascripts take 354.0 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 258.5 kB

  • Original 284.1 kB
  • After minification 283.9 kB
  • After compression 25.6 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 258.5 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 215.7 kB
  • After minification 215.7 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. L Barr images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.2 kB

  • Original 354.0 kB
  • After minification 354.0 kB
  • After compression 350.8 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.

Requests Breakdown

Number of requests can be reduced by 9 (56%)

Requests Now

16

After Optimization

7

  • AJAX
  • Images
  • JavaScript

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L Barr. 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 as a result speed up the page load time.

Network Requests Diagram

lbarr.com

lbarr.com

768 ms

c5b5e3973f54572788cd92556a7cb777.html

c5b5e3973f54572788cd92556a7cb777.html

509 ms

8217d7b.js

8217d7b.js

433 ms

be2eb8f.js

be2eb8f.js

57 ms

3cad222.js

3cad222.js

498 ms

e91af6b.js

e91af6b.js

477 ms

5f5098c.js

5f5098c.js

475 ms

1309c8a.js

1309c8a.js

498 ms

37b09eb.js

37b09eb.js

1042 ms

49dfb30.js

49dfb30.js

1637 ms

2c3a1b4.js

2c3a1b4.js

1127 ms

56fb7e.jpg

56fb7e.jpg

1329 ms

e17135.jpg

e17135.jpg

1389 ms

df4fff.jpg

df4fff.jpg

1403 ms

d4e990.jpg

d4e990.jpg

1917 ms

3d4bccaf5753e74748c4eebf53d7429f.svg

3d4bccaf5753e74748c4eebf53d7429f.svg

1570 ms

state.js

state.js

2270 ms

Accessibility Review

lbarr.com accessibility score

90

Accessibility Issues

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

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

SEO Factors

lbarr.com 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 Lbarr.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 Lbarr.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

lbarr.com

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