Report Summary

  • 0

    Performance

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

brianjdriscoll.com

Brian Driscoll

Page Load Speed

2.1 sec in total

First Response

466 ms

Resources Loaded

1.5 sec

Page Rendered

63 ms

About Website

Click here to check amazing Brian J Driscoll content. Otherwise, check out these important facts you probably never knew about brianjdriscoll.com

Documentary Photographer, currently based in New York City

Visit brianjdriscoll.com

Key Findings

We analyzed Brianjdriscoll.com page load time and found that the first response time was 466 ms and then it took 1.6 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

brianjdriscoll.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

brianjdriscoll.com

466 ms

site.css

126 ms

custom.css

109 ms

drYrzdPw2pARjMX-H3v-gyNlvnc3xDxj9eFe_--wrxMfe7wgfVQARMIPBQJDw2bt52sLFe4qFAmRweJXFhbhwyGTj14TjAo7ZY4TShFzde30jhNlOYiaikoKSc8ydcTqSc8DjhNCdfoRdhXKIAoDOAuzZfucdhoXOWF8ifXkH6qJ7mbbMg6IJMJ7fbK7mgMMeMt6MKG4fHl9IMMjgkMfH6qJnBbbMg6sJMJ7fbKzmgMMeMq6MKG4fOg9IMMjIkMfqMYycNxygb.js

699 ms

require.js

100 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original Brianjdriscoll.com, 50% (7 requests) were made to Use.typekit.net and 29% (4 requests) were made to Site.neonsky.com. The less responsive or slowest element that took the longest time to load (699 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.0 kB (12%)

Content Size

726.5 kB

After Optimization

636.6 kB

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

HTML Optimization

-82%

Potential reduce by 58.0 kB

  • Original 70.9 kB
  • After minification 69.0 kB
  • After compression 13.0 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 58.0 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 17.3 kB

  • Original 375.9 kB
  • After minification 358.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. Brian J Driscoll images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 13.2 kB

  • Original 243.7 kB
  • After minification 243.7 kB
  • After compression 230.5 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

-4%

Potential reduce by 1.5 kB

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

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

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

Accessibility Review

brianjdriscoll.com accessibility score

76

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

Image elements do not have [alt] attributes

Best Practices

brianjdriscoll.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

brianjdriscoll.com SEO score

75

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

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 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 Brianjdriscoll.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 Brianjdriscoll.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 Brian J Driscoll. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: