Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

benjaminallison.com

Benjamin Allison | Designer and illustrator in the SF Bay Area

Page Load Speed

2.4 sec in total

First Response

25 ms

Resources Loaded

1.4 sec

Page Rendered

949 ms

About Website

Welcome to benjaminallison.com homepage info - get ready to check Benjamin Allison best content right away, or after learning these important things about benjaminallison.com

Benjamin Allison is a designer specializing in branding, package design, and web design for clients in all industries, in particular, food and beverage.

Visit benjaminallison.com

Key Findings

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

Performance Metrics

benjaminallison.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

benjaminallison.com

25 ms

benjaminallison.com

885 ms

css2

57 ms

js

224 ms

autoptimize_755c46e9df067bd5e99683815241c8fe.css

39 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 61% of them (23 requests) were addressed to the original Benjaminallison.com, 16% (6 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (885 ms) belongs to the original domain Benjaminallison.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.8 kB (1%)

Content Size

3.4 MB

After Optimization

3.4 MB

In fact, the total size of Benjaminallison.com main page is 3.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 22.8 kB

  • Original 30.7 kB
  • After minification 30.7 kB
  • After compression 7.9 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 22.8 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 3.2 MB
  • After minification 3.2 MB

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. Benjamin Allison images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 589 B

  • Original 104.2 kB
  • After minification 104.2 kB
  • After compression 103.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 2 B

  • Original 114.5 kB
  • After minification 114.5 kB
  • After compression 114.5 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. Benjaminallison.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (40%)

Requests Now

30

After Optimization

18

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

Accessibility Review

benjaminallison.com accessibility score

71

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

benjaminallison.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

benjaminallison.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Benjaminallison.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 Benjaminallison.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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