Tools & Wizards About Us
brickley.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

brickley.com

Brickley Production Services | San Francisco | California |

Page Load Speed

2.5 sec in total

First Response

125 ms

Resources Loaded

2.3 sec

Page Rendered

54 ms

brickley.com screenshot

About Website

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

Brickley Production Services, meeting the rental needs of Film and Television productions large and small in the San Francisco bay area for over 30 years.

Visit brickley.com

Key Findings

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

brickley.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

www.brickley.com

125 ms

minified.js

43 ms

focus-within-polyfill.js

38 ms

polyfill.min.js

1386 ms

thunderbolt-commons.7700cd07.bundle.min.js

40 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Brickley.com, 40% (12 requests) were made to Static.parastorage.com and 37% (11 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.9 kB (32%)

Content Size

1.4 MB

After Optimization

954.9 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-72%

Potential reduce by 186.4 kB

  • Original 257.2 kB
  • After minification 255.6 kB
  • After compression 70.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 186.4 kB or 72% of the original size.

Image Optimization

-29%

Potential reduce by 257.8 kB

  • Original 886.5 kB
  • After minification 628.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. Obviously, Brickley needs image optimization as it can save up to 257.8 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 259.0 kB
  • After minification 259.0 kB
  • After compression 255.4 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 10 (56%)

Requests Now

18

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.brickley.com

www.brickley.com

125 ms

minified.js

minified.js

43 ms

focus-within-polyfill.js

focus-within-polyfill.js

38 ms

polyfill.min.js

polyfill.min.js

1386 ms

thunderbolt-commons.7700cd07.bundle.min.js

thunderbolt-commons.7700cd07.bundle.min.js

40 ms

main.16c08821.bundle.min.js

main.16c08821.bundle.min.js

69 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

38 ms

lodash.min.js

lodash.min.js

68 ms

react.production.min.js

react.production.min.js

68 ms

react-dom.production.min.js

react-dom.production.min.js

69 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

69 ms

15c462_863b53216b91459d9760fc776d8c1ed0~mv2.png

15c462_863b53216b91459d9760fc776d8c1ed0~mv2.png

540 ms

035244_6af9c4421a85482ca71b02dc782a276a~mv2.png

035244_6af9c4421a85482ca71b02dc782a276a~mv2.png

542 ms

035244_ad00e9a4df534dccbc20a627b0861168~mv2.png

035244_ad00e9a4df534dccbc20a627b0861168~mv2.png

635 ms

bundle.min.js

bundle.min.js

29 ms

92 ms

86 ms

88 ms

89 ms

84 ms

83 ms

120 ms

124 ms

120 ms

120 ms

118 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

22 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

5 ms

Accessibility Review

brickley.com accessibility score

98

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

Links do not have a discernible name

Best Practices

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

brickley.com SEO score

93

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

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

brickley.com

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