Tools & Wizards About Us
bridalallure.co.za screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

bridalallure.co.za

Bridal Wear Shop - Wedding Dresses in Cape Town - Bridal Allure

Page Load Speed

8.1 sec in total

First Response

1.1 sec

Resources Loaded

6.9 sec

Page Rendered

172 ms

bridalallure.co.za screenshot

About Website

Visit bridalallure.co.za now to see the best up-to-date Bridal Allure content for South Africa and also check out these interesting facts you probably never knew about bridalallure.co.za

We are wedding dress shop in South Africa. A large selection of carefully selected and exclusive evening and bridesmaid dresses on bridalallure.co.za

Visit bridalallure.co.za

Key Findings

We analyzed Bridalallure.co.za page load time and found that the first response time was 1.1 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

bridalallure.co.za performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

bridalallure.co.za

1095 ms

js

68 ms

gtm.js

108 ms

js

132 ms

widgetkit-6f37fa1a.css

711 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 62% of them (58 requests) were addressed to the original Bridalallure.co.za, 15% (14 requests) were made to Bridal-allure.co.za and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Bridal-allure.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 830.0 kB (17%)

Content Size

4.9 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bridalallure.co.za main page is 4.9 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. 40% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.6 kB

  • Original 71.6 kB
  • After minification 67.4 kB
  • After compression 15.0 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 56.6 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 39.6 kB

  • Original 3.8 MB
  • After minification 3.8 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. Bridal Allure images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 543.7 kB

  • Original 807.3 kB
  • After minification 768.2 kB
  • After compression 263.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 543.7 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 190.1 kB

  • Original 226.9 kB
  • After minification 203.7 kB
  • After compression 36.9 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. Bridalallure.co.za needs all CSS files to be minified and compressed as it can save up to 190.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (57%)

Requests Now

90

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bridalallure.co.za

bridalallure.co.za

1095 ms

js

js

68 ms

gtm.js

gtm.js

108 ms

js

js

132 ms

widgetkit-6f37fa1a.css

widgetkit-6f37fa1a.css

711 ms

e5996e84d6c1be1c3c08afad0f0850d1.css

e5996e84d6c1be1c3c08afad0f0850d1.css

489 ms

library-9edccb878f06d25f3a471c143221160b0.css

library-9edccb878f06d25f3a471c143221160b0.css

885 ms

default-9edccb878f06d25f3a471c143221160b0.css

default-9edccb878f06d25f3a471c143221160b0.css

887 ms

jquery.min.js

jquery.min.js

747 ms

jquery-noconflict.js

jquery-noconflict.js

374 ms

jquery-migrate.min.js

jquery-migrate.min.js

393 ms

caption.js

caption.js

544 ms

widgetkit-adfe8bb9.js

widgetkit-adfe8bb9.js

895 ms

mootools-core.js

mootools-core.js

1134 ms

core.js

core.js

841 ms

mootools-more.js

mootools-more.js

1668 ms

bootstrap.min.js

bootstrap.min.js

1234 ms

localdojo.js

localdojo.js

1456 ms

a20cc0d525557b6517fd3507d902eebd.js

a20cc0d525557b6517fd3507d902eebd.js

1462 ms

library-9edccb878f06d25f3a471c143221160b0.js

library-9edccb878f06d25f3a471c143221160b0.js

903 ms

default-9edccb878f06d25f3a471c143221160b0.js

default-9edccb878f06d25f3a471c143221160b0.js

907 ms

font-open_sanscondensed.css

font-open_sanscondensed.css

1269 ms

font-open_sansregular.css

font-open_sansregular.css

1508 ms

general.css

general.css

1604 ms

main.css

main.css

1900 ms

nav.css

nav.css

1831 ms

template.css

template.css

1837 ms

supersized.shutter.css

supersized.shutter.css

1883 ms

white-text.css

white-text.css

1981 ms

theme-black.css

theme-black.css

2059 ms

dynamic_css.php

dynamic_css.php

2194 ms

media_queries.css

media_queries.css

2331 ms

supersized.3.2.1.js

supersized.3.2.1.js

2355 ms

supersized.shutter.js

supersized.shutter.js

2264 ms

bootstrap.min.js

bootstrap.min.js

2475 ms

conversion.js

conversion.js

34 ms

addthis_widget.js

addthis_widget.js

143 ms

loader.js

loader.js

16 ms

css

css

27 ms

css

css

43 ms

lightbox.js

lightbox.js

1678 ms

spotlight.js

spotlight.js

1691 ms

fbds.js

fbds.js

63 ms

c1345a5f7b24875e1c1328ad8.js

c1345a5f7b24875e1c1328ad8.js

110 ms

icons8-whatsapp-75.png

icons8-whatsapp-75.png

247 ms

hanger.png

hanger.png

255 ms

twitter.png

twitter.png

366 ms

blogger.png

blogger.png

400 ms

facebook.png

facebook.png

449 ms

mail.png

mail.png

482 ms

instagram.png

instagram.png

608 ms

pinterest.png

pinterest.png

632 ms

youtube.png

youtube.png

758 ms

logo.png

logo.png

780 ms

white-20.png

white-20.png

783 ms

close.png

close.png

813 ms

magnifier.png

magnifier.png

943 ms

white-88.png

white-88.png

963 ms

join-us.png

join-us.png

1208 ms

centurygothic.woff

centurygothic.woff

1403 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

51 ms

44 ms

black-80.png

black-80.png

1163 ms

closebox.png

closebox.png

1178 ms

35 ms

back.png

back.png

1299 ms

forward.png

forward.png

1290 ms

openbox.png

openbox.png

1512 ms

white-40.png

white-40.png

1539 ms

thumb-back.png

thumb-back.png

1558 ms

thumb-forward.png

thumb-forward.png

1661 ms

53 ms

analytics.js

analytics.js

41 ms

000new_interior.jpg

000new_interior.jpg

1606 ms

001new_interior.jpg

001new_interior.jpg

1325 ms

002new_interior.jpg

002new_interior.jpg

1739 ms

003new_interior.jpg

003new_interior.jpg

1880 ms

004new_interior.jpg

004new_interior.jpg

1839 ms

100.jpg

100.jpg

1463 ms

101.jpg

101.jpg

2318 ms

102.jpg

102.jpg

2352 ms

103.jpg

103.jpg

2655 ms

104.jpg

104.jpg

2828 ms

progress.gif

progress.gif

1669 ms

close.png

close.png

1707 ms

blank.gif

blank.gif

1863 ms

31 ms

29 ms

collect

collect

14 ms

31 ms

32 ms

31 ms

js

js

58 ms

print.css

print.css

185 ms

Accessibility Review

bridalallure.co.za accessibility score

90

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best Practices

bridalallure.co.za best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

bridalallure.co.za SEO score

85

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

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 doesn't use 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 Bridalallure.co.za 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 Bridalallure.co.za 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

bridalallure.co.za

Open Graph description is not detected on the main page of Bridal Allure. 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: