Tools & Wizards About Us
brightlife.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

brightlife.com

Spiritual Development | Isle of Man | Brightlife Learning Centre & Spa

Page Load Speed

4.6 sec in total

First Response

262 ms

Resources Loaded

4 sec

Page Rendered

345 ms

brightlife.com screenshot

About Website

Visit brightlife.com now to see the best up-to-date Brightlife content for United Kingdom and also check out these interesting facts you probably never knew about brightlife.com

Luxury Spa, Spiritual Development, Personal Development, Workshops, Massage, Holistic Treatments, Wellbeing, Holistic Spa, Yoga & Pilates, Mindfulness, Learning, Isle of Man, Mind Body Spirit, Brightl...

Visit brightlife.com

Key Findings

We analyzed Brightlife.com page load time and found that the first response time was 262 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

brightlife.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value2,740 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

brightlife.com

262 ms

www.brightlife.com

1800 ms

index.php

592 ms

index.php

618 ms

font-awesome.min.css

180 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 44% of them (37 requests) were addressed to the original Brightlife.com, 14% (12 requests) were made to Maps.googleapis.com and 9% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Brightlife.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 591.2 kB (60%)

Content Size

990.9 kB

After Optimization

399.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brightlife.com main page is 990.9 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. 65% of websites need less resources to load. Javascripts take 698.8 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 20.9 kB

  • Original 28.7 kB
  • After minification 27.6 kB
  • After compression 7.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 20.9 kB or 73% of the original size.

Image Optimization

-24%

Potential reduce by 48.3 kB

  • Original 204.4 kB
  • After minification 156.1 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, Brightlife needs image optimization as it can save up to 48.3 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 472.6 kB

  • Original 698.8 kB
  • After minification 698.8 kB
  • After compression 226.1 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 472.6 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 49.3 kB

  • Original 59.0 kB
  • After minification 56.2 kB
  • After compression 9.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. Brightlife.com needs all CSS files to be minified and compressed as it can save up to 49.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (63%)

Requests Now

73

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brightlife.com

brightlife.com

262 ms

www.brightlife.com

www.brightlife.com

1800 ms

index.php

index.php

592 ms

index.php

index.php

618 ms

font-awesome.min.css

font-awesome.min.css

180 ms

frontend_default.css

frontend_default.css

263 ms

front.css

front.css

182 ms

modal.css

modal.css

240 ms

jquery.min.js

jquery.min.js

547 ms

jquery-noconflict.js

jquery-noconflict.js

299 ms

jquery-migrate.min.js

jquery-migrate.min.js

338 ms

bootstrap.min.js

bootstrap.min.js

437 ms

hikashop.js

hikashop.js

479 ms

script.js

script.js

518 ms

mootools-core.js

mootools-core.js

692 ms

core.js

core.js

569 ms

mootools-more-light.js

mootools-more-light.js

611 ms

modal.js

modal.js

645 ms

modal.image2.js

modal.image2.js

660 ms

uikit-7c708d43.js

uikit-7c708d43.js

989 ms

wk-scripts-e54a457d.js

wk-scripts-e54a457d.js

712 ms

bootstrap.css

bootstrap.css

785 ms

theme.css

theme.css

732 ms

custom.css

custom.css

752 ms

uikit.js

uikit.js

864 ms

autocomplete.js

autocomplete.js

788 ms

search.js

search.js

830 ms

sticky.js

sticky.js

850 ms

tooltip.js

tooltip.js

869 ms

social.js

social.js

882 ms

theme.js

theme.js

920 ms

css

css

76 ms

logo.png

logo.png

119 ms

drive_into_mist.jpg

drive_into_mist.jpg

818 ms

brightlife_house_web.jpg

brightlife_house_web.jpg

307 ms

embed

embed

123 ms

border_striped_horizontal.png

border_striped_horizontal.png

123 ms

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

100 ms

0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf

0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf

101 ms

MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf

MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf

123 ms

jZjuDZSb58pQtWhOr6q-6ALUuEpTyoUstqEm5AMlJo4.ttf

jZjuDZSb58pQtWhOr6q-6ALUuEpTyoUstqEm5AMlJo4.ttf

123 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

396 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

271 ms

analytics.js

analytics.js

101 ms

widgets.js

widgets.js

27 ms

plusone.js

plusone.js

91 ms

sdk.js

sdk.js

314 ms

js

js

111 ms

init_embed.js

init_embed.js

55 ms

collect

collect

29 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

37 ms

common.js

common.js

94 ms

map.js

map.js

95 ms

google4.png

google4.png

53 ms

overlay.js

overlay.js

50 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

115 ms

90 ms

util.js

util.js

65 ms

onion.js

onion.js

63 ms

stats.js

stats.js

61 ms

openhand_8_8.cur

openhand_8_8.cur

52 ms

xd_arbiter.php

xd_arbiter.php

233 ms

xd_arbiter.php

xd_arbiter.php

437 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

60 ms

controls.js

controls.js

56 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

53 ms

kh

kh

131 ms

transparent.png

transparent.png

46 ms

css

css

58 ms

entity11.png

entity11.png

53 ms

vt

vt

45 ms

vt

vt

48 ms

vt

vt

46 ms

vt

vt

53 ms

vt

vt

44 ms

vt

vt

46 ms

mapcnt6.png

mapcnt6.png

41 ms

sv5.png

sv5.png

43 ms

vt

vt

50 ms

tmapctrl.png

tmapctrl.png

35 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

7 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

7 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

7 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

48 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

48 ms

Accessibility Review

brightlife.com accessibility score

87

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

Buttons do not have an accessible name

High

Links do not have a discernible 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

Best Practices

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

brightlife.com SEO score

98

Search Engine Optimization Advices

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

brightlife.com

Open Graph description is not detected on the main page of Brightlife. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: