Tools & Wizards About Us
brianrothenberg.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

brianrothenberg.com

Brian Rothenberg .com – Startup growth – strategy, product, marketing, analytics, investing, and the intersection of them all.

Page Load Speed

2.2 sec in total

First Response

9 ms

Resources Loaded

1.7 sec

Page Rendered

506 ms

brianrothenberg.com screenshot

About Website

Welcome to brianrothenberg.com homepage info - get ready to check Brian Rothenberg best content right away, or after learning these important things about brianrothenberg.com

Startup growth – strategy, product, marketing, analytics, investing, and the intersection of them all.

Visit brianrothenberg.com

Key Findings

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

brianrothenberg.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

brianrothenberg.com

9 ms

brianrothenberg.com

207 ms

twentysixteen.css

84 ms

97 ms

91 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Brianrothenberg.com, 26% (16 requests) were made to S2.wp.com and 21% (13 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Brianrothenbergcom.files.wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.1 kB (5%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brianrothenberg.com main page is 1.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 66.0 kB

  • Original 87.8 kB
  • After minification 85.6 kB
  • After compression 21.8 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 66.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 409 B

  • Original 1.3 MB
  • After minification 1.3 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. Brian Rothenberg images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 1.2 kB

  • Original 26.9 kB
  • After minification 26.9 kB
  • After compression 25.7 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

-1%

Potential reduce by 476 B

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

Requests Breakdown

Number of requests can be reduced by 29 (57%)

Requests Now

51

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brianrothenberg.com

brianrothenberg.com

9 ms

brianrothenberg.com

brianrothenberg.com

207 ms

twentysixteen.css

twentysixteen.css

84 ms

97 ms

91 ms

86 ms

115 ms

block-editor.css

block-editor.css

105 ms

91 ms

101 ms

global.css

global.css

100 ms

101 ms

hovercards.min.js

hovercards.min.js

102 ms

wpgroho.js

wpgroho.js

102 ms

97 ms

w.js

w.js

131 ms

from_zero_to_ipo__how_growth_needs_to_evolve_at_every_startup_stage___first_round_review.png

from_zero_to_ipo__how_growth_needs_to_evolve_at_every_startup_stage___first_round_review.png

736 ms

b586fa56960e4a984a3f5185af3b9a9a0b092638500375d6185bafba24d2f7d1

b586fa56960e4a984a3f5185af3b9a9a0b092638500375d6185bafba24d2f7d1

55 ms

454 ms

474 ms

widgets.js

widgets.js

113 ms

intercom-headshot-brian-rothenberg.png

intercom-headshot-brian-rothenberg.png

708 ms

brian-and-casey-greylock-marketplaces-podcast.jpeg

brian-and-casey-greylock-marketplaces-podcast.jpeg

240 ms

frc-header.png

frc-header.png

1341 ms

brian-rothenberg-headshot-frc.jpg

brian-rothenberg-headshot-frc.jpg

402 ms

growth-curve.png

growth-curve.png

191 ms

g.gif

g.gif

62 ms

remote-login.php

remote-login.php

102 ms

g.gif

g.gif

56 ms

g.gif

g.gif

57 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

84 ms

montserrat-all-700-normal.woff

montserrat-all-700-normal.woff

5 ms

montserrat-all-400-normal.woff

montserrat-all-400-normal.woff

4 ms

merriweather-all-400-normal.woff

merriweather-all-400-normal.woff

5 ms

merriweather-all-700-normal.woff

merriweather-all-700-normal.woff

6 ms

merriweather-all-900-normal.woff

merriweather-all-900-normal.woff

18 ms

merriweather-all-400-italic.woff

merriweather-all-400-italic.woff

21 ms

merriweather-all-700-italic.woff

merriweather-all-700-italic.woff

20 ms

merriweather-all-900-italic.woff

merriweather-all-900-italic.woff

20 ms

Genericons.svg

Genericons.svg

20 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

5 ms

settings

settings

69 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

25 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

53 ms

embeds

embeds

22 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

57 ms

bmrothenberg

bmrothenberg

96 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

26 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

25 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

267 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

264 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

279 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

279 ms

_buildManifest.js

_buildManifest.js

301 ms

_ssgManifest.js

_ssgManifest.js

301 ms

widget-7-0f68f768293f.js

widget-7-0f68f768293f.js

28 ms

widget-8-c2925473b3d9.js

widget-8-c2925473b3d9.js

29 ms

widget-9-5cc399d6bead.js

widget-9-5cc399d6bead.js

43 ms

logo-200x120-3190df52.png

logo-200x120-3190df52.png

41 ms

widget-0-fbbfd8d3246a.js

widget-0-fbbfd8d3246a.js

28 ms

actionbar.css

actionbar.css

2 ms

actionbar.js

actionbar.js

21 ms

Accessibility Review

brianrothenberg.com accessibility score

91

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

High

Links do not have a discernible name

Best Practices

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

High

Page has valid source maps

SEO Factors

brianrothenberg.com SEO score

83

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brianrothenberg.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 Brianrothenberg.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

brianrothenberg.com

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