Access whereisbrad.com. Where is Brad

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

390 ms

web-animations-next-lite.min.js

16 ms

webcomponents-all-noPatch.js

24 ms

fetch-polyfill.js

13 ms

intersection-observer.min.js

12 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whereisbrad.com, 19% (4 requests) were made to Fonts.gstatic.com and 10% (2 requests) were made to Accounts.google.com. The less responsive or slowest element that took the longest time to load (390 ms) relates to the external source Youtube.com.

Content Size

1.4 MB

After Optimization

268.6 kB

In fact, the total size of Whereisbrad.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. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 919.6 kB

Original 1.1 MB
After minification 1.1 MB
After compression 181.7 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 919.6 kB or 83% of the original size.

JavaScript Optimization

-69%

Potential reduce by 185.5 kB

Original 270.4 kB
After minification 269.3 kB
After compression 84.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 185.5 kB or 69% of the original size.

CSS Optimization

-79%

Potential reduce by 7.3 kB

Original 9.3 kB
After minification 9.3 kB
After compression 2.0 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. Whereisbrad.com needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 79% of the original size.

Requests Now

After Optimization

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Where Is Brad. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

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 Whereisbrad.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 Whereisbrad.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 Where Is Brad. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: