Tools & Wizards About Us
bright.how screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

bright.how

The One Simple Change to Have Lasting Peace and Freedom from Suffering

Page Load Speed

2.7 sec in total

First Response

102 ms

Resources Loaded

1.9 sec

Page Rendered

655 ms

bright.how screenshot

About Website

Visit bright.how now to see the best up-to-date Bright content for United States and also check out these interesting facts you probably never knew about bright.how

Access our free Online Training to reveal the secret to inner peace and complete freedom even if you have health, relationship or career challenges.

Visit bright.how

Key Findings

We analyzed Bright.how page load time and found that the first response time was 102 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

bright.how performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value2,350 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

bright.how

102 ms

www.bright.how

644 ms

bootstrap.min.css

92 ms

font-awesome.min.css

98 ms

css

102 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Bright.how, 31% (10 requests) were made to Kajabi-storefronts-production.kajabi-cdn.com and 13% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (918 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.6 kB (3%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 33.6 kB

  • Original 45.0 kB
  • After minification 40.2 kB
  • After compression 11.4 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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.6 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 4.3 kB

  • Original 899.6 kB
  • After minification 895.3 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. Bright images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 273.5 kB
  • After minification 273.5 kB
  • After compression 270.6 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

-24%

Potential reduce by 1.8 kB

  • Original 7.6 kB
  • After minification 7.6 kB
  • After compression 5.7 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. Bright.how needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (62%)

Requests Now

26

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bright.how

bright.how

102 ms

www.bright.how

www.bright.how

644 ms

bootstrap.min.css

bootstrap.min.css

92 ms

font-awesome.min.css

font-awesome.min.css

98 ms

css

css

102 ms

core-4d08d258547af8a29fc4738e545ca8e26d95e11b829a9db5a0b36d047fb91843.css

core-4d08d258547af8a29fc4738e545ca8e26d95e11b829a9db5a0b36d047fb91843.css

128 ms

styles.css

styles.css

155 ms

cookieinfo.min.js

cookieinfo.min.js

99 ms

js

js

139 ms

api.js

api.js

102 ms

core-a677e5a363d40f76b3718d199d48f3d579df4c7aa8a9543dab773eea7c8017bf.js

core-a677e5a363d40f76b3718d199d48f3d579df4c7aa8a9543dab773eea7c8017bf.js

178 ms

E-v1.js

E-v1.js

108 ms

plugin.js

plugin.js

111 ms

ouibounce.min.js

ouibounce.min.js

98 ms

slick.min.js

slick.min.js

106 ms

scripts.js

scripts.js

354 ms

tether.min.js

tether.min.js

111 ms

bootstrap.min.js

bootstrap.min.js

99 ms

polyfill.min.js

polyfill.min.js

918 ms

fbevents.js

fbevents.js

227 ms

ff3MtLSRKqT3KhTsamO2_SM_Logo_Horizontal_Maroon_Small.png

ff3MtLSRKqT3KhTsamO2_SM_Logo_Horizontal_Maroon_Small.png

213 ms

BZImDJI8QwSkkQxKPXwd_SM_banner_fb_rainbow_lrg.jpg

BZImDJI8QwSkkQxKPXwd_SM_banner_fb_rainbow_lrg.jpg

212 ms

custom.jpg

custom.jpg

251 ms

showcase.jpg

showcase.jpg

252 ms

CstpRmgtSpKVemisdvWB_Eric_Kim_Circle_2_500x500px.jpg

CstpRmgtSpKVemisdvWB_Eric_Kim_Circle_2_500x500px.jpg

250 ms

33Mijd9nSeC2J52DvFl8_W6lRYONnRKa5YtGroSK9_brillaint-community-sonia-min_1_.png

33Mijd9nSeC2J52DvFl8_W6lRYONnRKa5YtGroSK9_brillaint-community-sonia-min_1_.png

251 ms

c65aa6d-2a86-a4ca-011b-a8d231abe8_jonathan.jpg

c65aa6d-2a86-a4ca-011b-a8d231abe8_jonathan.jpg

403 ms

EuAGrTZRT0qyOjZKEl4s_Samantha_Loff_2_Round_500x500px.png

EuAGrTZRT0qyOjZKEl4s_Samantha_Loff_2_Round_500x500px.png

281 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

84 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

103 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0oA.woff

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0oA.woff

117 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0oA.woff

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0oA.woff

120 ms

Accessibility Review

bright.how accessibility score

54

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

bright.how best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

bright.how SEO score

86

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 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 Bright.how 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 Bright.how 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

bright.how

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