Tools & Wizards About Us
brillea.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

brillea.com

brillea - helping purpose-driven startups launch & grow

Page Load Speed

1.5 sec in total

First Response

234 ms

Resources Loaded

770 ms

Page Rendered

483 ms

brillea.com screenshot

About Website

Visit brillea.com now to see the best up-to-date Brillea content and also check out these interesting facts you probably never knew about brillea.com

Acquire new customers from Facebook, Instagram and Google for £699 a month. Let brillea create, manage and optimise your ads

Visit brillea.com

Key Findings

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

Performance Metrics

brillea.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.26

47/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

brillea.com

234 ms

css

28 ms

polyfill-b4083633ea2b540779c1.js

170 ms

component---src-pages-index-jsx-47c62f40d3e220250c98.js

100 ms

6961d6ad99ef4e152a0741e6295558b9c6335267-e6f85f1cc4f29a007143.js

147 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 82% of them (32 requests) were addressed to the original Brillea.com, 8% (3 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (416 ms) belongs to the original domain Brillea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 394.1 kB (41%)

Content Size

956.8 kB

After Optimization

562.7 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-81%

Potential reduce by 275.0 kB

  • Original 339.8 kB
  • After minification 339.7 kB
  • After compression 64.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 275.0 kB or 81% of the original size.

Image Optimization

-19%

Potential reduce by 119.1 kB

  • Original 614.8 kB
  • After minification 495.7 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, Brillea needs image optimization as it can save up to 119.1 kB or 19% 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 12 B

  • Original 2.2 kB
  • After minification 2.2 kB
  • After compression 2.2 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 15 (44%)

Requests Now

34

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brillea.com

brillea.com

234 ms

css

css

28 ms

polyfill-b4083633ea2b540779c1.js

polyfill-b4083633ea2b540779c1.js

170 ms

component---src-pages-index-jsx-47c62f40d3e220250c98.js

component---src-pages-index-jsx-47c62f40d3e220250c98.js

100 ms

6961d6ad99ef4e152a0741e6295558b9c6335267-e6f85f1cc4f29a007143.js

6961d6ad99ef4e152a0741e6295558b9c6335267-e6f85f1cc4f29a007143.js

147 ms

dfcef0090c1190ed93c8e360ab82d232a8b0998c-46cd43d8fd069b2da13c.js

dfcef0090c1190ed93c8e360ab82d232a8b0998c-46cd43d8fd069b2da13c.js

106 ms

df745e1d2b1c1caaacccad9c58766eaebd17e108-301f7487d54abf65d4c9.js

df745e1d2b1c1caaacccad9c58766eaebd17e108-301f7487d54abf65d4c9.js

64 ms

d97f4153cdf402558da09ba538546613659f2c80-d01e8733b13887508a6b.js

d97f4153cdf402558da09ba538546613659f2c80-d01e8733b13887508a6b.js

62 ms

commons-abb2c7eb24a06586282e.js

commons-abb2c7eb24a06586282e.js

147 ms

app-896ba0dc2cf30e125be4.js

app-896ba0dc2cf30e125be4.js

214 ms

dc6a8720040df98778fe970bf6c000a41750d3ae-9598bf7a34b2a835ee89.js

dc6a8720040df98778fe970bf6c000a41750d3ae-9598bf7a34b2a835ee89.js

184 ms

cb1608f2-860a802ffba44cbf12ba.js

cb1608f2-860a802ffba44cbf12ba.js

201 ms

framework-ddc4a3be961269111282.js

framework-ddc4a3be961269111282.js

165 ms

styles-474c0340beb1ced255f1.js

styles-474c0340beb1ced255f1.js

166 ms

webpack-runtime-356959e724faf4790679.js

webpack-runtime-356959e724faf4790679.js

278 ms

gtm.js

gtm.js

87 ms

Header_graphic-e8baed7a2898d1e8e08e992974a08aa9.png

Header_graphic-e8baed7a2898d1e8e08e992974a08aa9.png

324 ms

people-dde2e709ff8e65ef9107638182e1d546.png

people-dde2e709ff8e65ef9107638182e1d546.png

225 ms

tech-ad50985bbaa890588d59ff2e296a5dfb.png

tech-ad50985bbaa890588d59ff2e296a5dfb.png

316 ms

ReasonsToBelieve_icon_CleverTech.980c4b4e.svg

ReasonsToBelieve_icon_CleverTech.980c4b4e.svg

168 ms

ReasonsToBelieve_icon_Knowledge.934996a0.svg

ReasonsToBelieve_icon_Knowledge.934996a0.svg

219 ms

ReasonsToBelieve_icon_MarketingExpert.daee5bee.svg

ReasonsToBelieve_icon_MarketingExpert.daee5bee.svg

222 ms

ReasonsToBelieve_icon_Pause.08eb7fd6.svg

ReasonsToBelieve_icon_Pause.08eb7fd6.svg

319 ms

image_MadeForDrink_Ad-6f26c1393f860256acc9ec7b8c6dba23.png

image_MadeForDrink_Ad-6f26c1393f860256acc9ec7b8c6dba23.png

322 ms

speedo_white-e9177e1acbbe5552f32a1df55e80a6b6.png

speedo_white-e9177e1acbbe5552f32a1df55e80a6b6.png

318 ms

vodafone_white-9ff98fe723a90abe81e1a315e484fce7.png

vodafone_white-9ff98fe723a90abe81e1a315e484fce7.png

321 ms

checkatrade_white-f089dc3e1b70731698b751c1e068f9fe.png

checkatrade_white-f089dc3e1b70731698b751c1e068f9fe.png

352 ms

westfield_white-4162a22eb528f0a95cb03c9e56b534a1.png

westfield_white-4162a22eb528f0a95cb03c9e56b534a1.png

415 ms

moonpig_white-20461d0e24316e803e00a0146c30c37e.png

moonpig_white-20461d0e24316e803e00a0146c30c37e.png

416 ms

smarty_white-e0d7a5acd7e8829fdf2e924a0a544972.png

smarty_white-e0d7a5acd7e8829fdf2e924a0a544972.png

352 ms

azimo_white-8bbd773cb6b1fe1262bd49c03d6baff4.png

azimo_white-8bbd773cb6b1fe1262bd49c03d6baff4.png

351 ms

telefonica_white-19c82f9da9d198346e6d7490ef475b02.png

telefonica_white-19c82f9da9d198346e6d7490ef475b02.png

415 ms

core.js

core.js

26 ms

8444163.js

8444163.js

110 ms

K2FifZFYk-dHSE0UPPuwQ7CrD94i-NCKm-U48M1wqxnG.ttf

K2FifZFYk-dHSE0UPPuwQ7CrD94i-NCKm-U48M1wqxnG.ttf

100 ms

7cHqv4kjgoGqM7E3p-ks51op.ttf

7cHqv4kjgoGqM7E3p-ks51op.ttf

128 ms

7cHqv4kjgoGqM7E3_-gs51op.ttf

7cHqv4kjgoGqM7E3_-gs51op.ttf

154 ms

47-4aa5b344dbba6a156e35.js

47-4aa5b344dbba6a156e35.js

71 ms

app-data.json

app-data.json

67 ms

Accessibility Review

brillea.com accessibility score

78

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-*] attributes do not match their roles

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

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

High

Page has valid source maps

SEO Factors

brillea.com SEO score

85

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

brillea.com

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