Tools & Wizards About Us
weddingfares.co.uk screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

weddingfares.co.uk

Wedding Fares | Wedding Dresses | Wedding Cars | West Midlands

Page Load Speed

3.7 sec in total

First Response

251 ms

Resources Loaded

3.1 sec

Page Rendered

373 ms

weddingfares.co.uk screenshot

About Website

Click here to check amazing Wedding Fares content. Otherwise, check out these important facts you probably never knew about weddingfares.co.uk

Wedding Fares: Here at Wedding Fayres West Midlands, we can solve all of your wedding day problems, you can simply select which county you live...

Visit weddingfares.co.uk

Key Findings

We analyzed Weddingfares.co.uk page load time and found that the first response time was 251 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

weddingfares.co.uk performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.466

19/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

weddingfares.co.uk

251 ms

www.weddingfares.co.uk

930 ms

style.css

83 ms

content.css

165 ms

073782fc883843f282ab37b26da6d8fb_0.js

402 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 65% of them (69 requests) were addressed to the original Weddingfares.co.uk, 10% (11 requests) were made to Cdnjs.cloudflare.com and 9% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Weddingfares.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 460.8 kB (13%)

Content Size

3.5 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weddingfares.co.uk main page is 3.5 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. 70% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 74.3 kB

  • Original 94.6 kB
  • After minification 91.2 kB
  • After compression 20.3 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 74.3 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 274.4 kB

  • Original 2.7 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. Wedding Fares images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 66.9 kB

  • Original 473.7 kB
  • After minification 473.7 kB
  • After compression 406.9 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 66.9 kB or 14% of the original size.

CSS Optimization

-24%

Potential reduce by 45.3 kB

  • Original 186.1 kB
  • After minification 186.1 kB
  • After compression 140.8 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. Weddingfares.co.uk needs all CSS files to be minified and compressed as it can save up to 45.3 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (78%)

Requests Now

90

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weddingfares.co.uk

weddingfares.co.uk

251 ms

www.weddingfares.co.uk

www.weddingfares.co.uk

930 ms

style.css

style.css

83 ms

content.css

content.css

165 ms

073782fc883843f282ab37b26da6d8fb_0.js

073782fc883843f282ab37b26da6d8fb_0.js

402 ms

script.js

script.js

247 ms

073782fc883843f282ab37b26da6d8fb_1.js

073782fc883843f282ab37b26da6d8fb_1.js

326 ms

073782fc883843f282ab37b26da6d8fb_2.js

073782fc883843f282ab37b26da6d8fb_2.js

252 ms

529bc181c4e2bf7035c25e1dc4a4cafa_0.css

529bc181c4e2bf7035c25e1dc4a4cafa_0.css

444 ms

smartslider.min.css

smartslider.min.css

254 ms

n2-j.min.js

n2-j.min.js

400 ms

nextend-gsap.min.js

nextend-gsap.min.js

442 ms

nextend-frontend.min.js

nextend-frontend.min.js

334 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

443 ms

smartslider-simple-type-frontend.min.js

smartslider-simple-type-frontend.min.js

469 ms

bootstrap-default-min.css

bootstrap-default-min.css

484 ms

bootstrap-responsive.css

bootstrap-responsive.css

485 ms

font-awesome.min.css

font-awesome.min.css

499 ms

ionicons.min.css

ionicons.min.css

496 ms

css

css

72 ms

s5_flex_menu-min.js

s5_flex_menu-min.js

500 ms

s5_flex_menu.css

s5_flex_menu.css

502 ms

system.css

system.css

560 ms

general.css

general.css

562 ms

template.css

template.css

576 ms

editor.css

editor.css

582 ms

thirdparty.css

thirdparty.css

580 ms

css

css

90 ms

multibox.css

multibox.css

584 ms

ajax.css

ajax.css

661 ms

overlay.js

overlay.js

667 ms

multibox.js

multibox.js

721 ms

s5_responsive_bars-min.css

s5_responsive_bars-min.css

718 ms

s5_responsive_hide_classes-min.css

s5_responsive_hide_classes-min.css

721 ms

s5_responsive.css

s5_responsive.css

719 ms

custom.css

custom.css

742 ms

scrollReveal-min.js

scrollReveal-min.js

745 ms

s5_columns_equalizer-min.js

s5_columns_equalizer-min.js

820 ms

css

css

89 ms

css_bootstrap.css

css_bootstrap.css

831 ms

sweetalert.min.js

sweetalert.min.js

90 ms

jquery-confirm.min.css

jquery-confirm.min.css

90 ms

jquery-confirm.min.js

jquery-confirm.min.js

98 ms

bootstrap-theme.min.css

bootstrap-theme.min.css

107 ms

bootstrap-datepicker3.min.css

bootstrap-datepicker3.min.css

115 ms

font-awesome.min.css

font-awesome.min.css

82 ms

css

css

86 ms

css

css

88 ms

cookieconsent.min.css

cookieconsent.min.css

100 ms

cookieconsent.min.js

cookieconsent.min.js

90 ms

js

js

118 ms

jquery.min.js

jquery.min.js

75 ms

bootstrap.min.js

bootstrap.min.js

127 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

341 ms

jquery.validate.min.js

jquery.validate.min.js

74 ms

additional-methods.min.js

additional-methods.min.js

73 ms

jquery.scrollTo.min.js

jquery.scrollTo.min.js

100 ms

_all.min.css

_all.min.css

92 ms

icheck.min.js

icheck.min.js

108 ms

select2.min.css

select2.min.css

97 ms

select2.full.min.js

select2.full.min.js

116 ms

typeahead.bundle.min.js

typeahead.bundle.min.js

128 ms

js

js

118 ms

lity.css

lity.css

814 ms

custom2.css

custom2.css

765 ms

sweetalert.min.js

sweetalert.min.js

23 ms

custom3.css

custom3.css

685 ms

custom4.css

custom4.css

605 ms

lity.js

lity.js

658 ms

search.js

search.js

656 ms

functions.js

functions.js

804 ms

mail.js

mail.js

815 ms

crafty_postcode.class.js

crafty_postcode.class.js

537 ms

s5_responsive_mobile_bar-min.js

s5_responsive_mobile_bar-min.js

496 ms

vendor.js

vendor.js

541 ms

jqueryform.com.min.js

jqueryform.com.min.js

559 ms

logo.png

logo.png

542 ms

wedding-bells.png

wedding-bells.png

593 ms

wedding-slide4.jpg

wedding-slide4.jpg

878 ms

wedding-slide2.jpg

wedding-slide2.jpg

872 ms

wedding-slide3.jpg

wedding-slide3.jpg

767 ms

wedding-cake.jpg

wedding-cake.jpg

655 ms

wedding-dress.jpg

wedding-dress.jpg

788 ms

system.css

system.css

673 ms

venue.jpg

venue.jpg

757 ms

flowers3.jpg

flowers3.jpg

959 ms

wedding-car.jpg

wedding-car.jpg

789 ms

heart.jpg

heart.jpg

824 ms

Liliann_Banner.png

Liliann_Banner.png

1006 ms

greyhound.png

greyhound.png

894 ms

Avoncroft_banner.png

Avoncroft_banner.png

887 ms

dancers_banner.png

dancers_banner.png

865 ms

search_light.png

search_light.png

250 ms

menu_light.png

menu_light.png

345 ms

s5_scroll_arrow.png

s5_scroll_arrow.png

267 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

54 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

54 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

172 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

184 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

186 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

184 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

186 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

186 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

499 ms

sykt-z54laciWfKv-kX8krex0jDiD2HbY6IJshzT.ttf

sykt-z54laciWfKv-kX8krex0jDiD2HbY6IJshzT.ttf

187 ms

ionicons.ttf

ionicons.ttf

267 ms

Accessibility Review

weddingfares.co.uk accessibility score

94

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

Heading elements are not in a sequentially-descending order

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

weddingfares.co.uk 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

SEO Factors

weddingfares.co.uk SEO score

71

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

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 Weddingfares.co.uk 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 Weddingfares.co.uk 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

weddingfares.co.uk

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