Access brilliantbridal.com. Brilliant Bridal

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

www.brilliantbridal.com

62 ms

hdg0phe.css

28 ms

js

125 ms

theme.min.css

24 ms

theme.min.js

217 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 76% of them (54 requests) were addressed to the original Brilliantbridal.com, 18% (13 requests) were made to Use.typekit.net and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (239 ms) belongs to the original domain Brilliantbridal.com.

Content Size

3.3 MB

After Optimization

3.1 MB

In fact, the total size of Brilliantbridal.com main page is 3.3 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. Only a small number of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 75.4 kB

Original 86.0 kB
After minification 61.2 kB
After compression 10.6 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 24.8 kB, which is 29% 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 75.4 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 43.8 kB

Original 2.4 MB
After minification 2.4 MB

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. Brilliant Bridal images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 88.4 kB

Original 652.9 kB
After minification 652.9 kB
After compression 564.5 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 88.4 kB or 14% of the original size.

CSS Optimization

-23%

Potential reduce by 45.2 kB

Original 199.3 kB
After minification 199.3 kB
After compression 154.1 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. Brilliantbridal.com needs all CSS files to be minified and compressed as it can save up to 45.2 kB or 23% of the original size.

Requests Now

After Optimization

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brilliant Bridal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts 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-*] attributes do not match their roles

High

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

High

[role]s are not contained by their required parent element

High

[aria-*] attributes are not valid or misspelled

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

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

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

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

brilliantbridal.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Brilliant Bridal

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.brilliantbridal.com

hdg0phe.css

js

theme.min.css

theme.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.brilliantbridal.com

hdg0phe.css

js

theme.min.css

theme.min.js

js

p.css

fbevents.js

main-logo

b469131b874f4f0698e170882054cb49.webp

d900315ed32045b1b856dad42720c309.webp

54d892599cf9415ebf85ce2d69a59f30.webp

9f001ac6120d4685bc0e9bda4746e51c.webp

95275315dfe5452c8f86480e8c868cf2.webp

b280b2d736bb49748b26016e257f1fdc.webp

0f15ef30_5ed5_4ab6_8c2d_e1f0c72aa2d6.jpg

41e47d20_080e_47ef_9486_148d3830e679.jpg

savings.jpg

mesa.jpg

Brilliant_Bridal_Dallas.jpeg

Brilliant-Bridal-Sparkling-Saturday-Dgass-Photography-02307.jpg

outdoor_smaller.webp

location5.jpg

houston_1-4.webp

designer1.jpg

EddyKHomepage.jpg

CasablancaHomepage.jpg

watters.jpg

ballgown.jpg

coltype4.jpg

straplesshomepage.jpg

lowback.jpg

brilliant-brides-text.svg

bride1.jpg

bride2.jpg

bride2-mobile.jpg

bride3.jpg

17983098425004027.webp

18048781009416628.webp

17850258293934835.webp

17950796009391305.webp

18205391245243414.webp

17982336878071329.webp