Tools & Wizards About Us
bartlehall.co.uk screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

bartlehall.co.uk

Wedding Venue in Preston & Lancashire | Country House Hotel

Page Load Speed

4.4 sec in total

First Response

267 ms

Resources Loaded

2.7 sec

Page Rendered

1.4 sec

bartlehall.co.uk screenshot

About Website

Welcome to bartlehall.co.uk homepage info - get ready to check Bartlehall best content right away, or after learning these important things about bartlehall.co.uk

The perfect wedding venue in Preston, Lancashire. This unique country house hotel is situated between Preston and Blackpool. Contact our team today.

Visit bartlehall.co.uk

Key Findings

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

Performance Metrics

bartlehall.co.uk performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value21.9 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value1,800 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

bartlehall.co.uk

267 ms

bartlehall.co.uk

431 ms

gravity-forms-theme-reset.min.css

83 ms

gravity-forms-theme-foundation.min.css

167 ms

gravity-forms-theme-framework.min.css

329 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 91% of them (89 requests) were addressed to the original Bartlehall.co.uk, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Solene.qodeinteractive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 493.6 kB (5%)

Content Size

9.7 MB

After Optimization

9.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bartlehall.co.uk main page is 9.7 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 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 145.9 kB

  • Original 181.5 kB
  • After minification 174.6 kB
  • After compression 35.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. 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 145.9 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 25.9 kB

  • Original 8.3 MB
  • After minification 8.3 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. Bartlehall images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 3.2 kB

  • Original 658.3 kB
  • After minification 658.3 kB
  • After compression 655.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. This website has mostly compressed JavaScripts.

CSS Optimization

-59%

Potential reduce by 318.7 kB

  • Original 538.2 kB
  • After minification 537.5 kB
  • After compression 219.5 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. Bartlehall.co.uk needs all CSS files to be minified and compressed as it can save up to 318.7 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (79%)

Requests Now

92

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bartlehall.co.uk

bartlehall.co.uk

267 ms

bartlehall.co.uk

bartlehall.co.uk

431 ms

gravity-forms-theme-reset.min.css

gravity-forms-theme-reset.min.css

83 ms

gravity-forms-theme-foundation.min.css

gravity-forms-theme-foundation.min.css

167 ms

gravity-forms-theme-framework.min.css

gravity-forms-theme-framework.min.css

329 ms

animate.min.css

animate.min.css

253 ms

lc-public.css

lc-public.css

259 ms

grid.css

grid.css

271 ms

main.css

main.css

273 ms

style.css

style.css

335 ms

modules.min.css

modules.min.css

503 ms

dripicons.css

dripicons.css

360 ms

style.min.css

style.min.css

367 ms

fontawesome-all.min.css

fontawesome-all.min.css

364 ms

ionicons.min.css

ionicons.min.css

410 ms

style.css

style.css

417 ms

style.css

style.css

448 ms

simple-line-icons.css

simple-line-icons.css

454 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

456 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

491 ms

style_dynamic.css

style_dynamic.css

498 ms

modules-responsive.min.css

modules-responsive.min.css

535 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

544 ms

css

css

38 ms

core-dashboard.min.css

core-dashboard.min.css

547 ms

js_composer.min.css

js_composer.min.css

658 ms

breeze-prefetch-links.min.js

breeze-prefetch-links.min.js

588 ms

jquery.min.js

jquery.min.js

588 ms

jquery-migrate.min.js

jquery-migrate.min.js

624 ms

jquery.json.min.js

jquery.json.min.js

634 ms

gravityforms.min.js

gravityforms.min.js

637 ms

conditional_logic.min.js

conditional_logic.min.js

754 ms

chosen.jquery.min.js

chosen.jquery.min.js

755 ms

utils.min.js

utils.min.js

755 ms

js

js

51 ms

js

js

84 ms

css

css

33 ms

button.css

button.css

754 ms

rs6.css

rs6.css

755 ms

main.js

main.js

771 ms

api.js

api.js

86 ms

rbtools.min.js

rbtools.min.js

848 ms

rs6.min.js

rs6.min.js

812 ms

core.min.js

core.min.js

690 ms

tabs.min.js

tabs.min.js

604 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

686 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

601 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

634 ms

jquery.appear.js

jquery.appear.js

666 ms

modernizr.min.js

modernizr.min.js

626 ms

hoverIntent.min.js

hoverIntent.min.js

624 ms

owl.carousel.min.js

owl.carousel.min.js

608 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

627 ms

fluidvids.min.js

fluidvids.min.js

641 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

601 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

587 ms

parallax.min.js

parallax.min.js

560 ms

jquery.waitforimages.js

jquery.waitforimages.js

572 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

618 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

596 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

591 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

574 ms

swiper.min.js

swiper.min.js

573 ms

modules.min.js

modules.min.js

571 ms

dom-ready.min.js

dom-ready.min.js

643 ms

hooks.min.js

hooks.min.js

601 ms

i18n.min.js

i18n.min.js

601 ms

a11y.min.js

a11y.min.js

567 ms

vendor-theme.min.js

vendor-theme.min.js

567 ms

scripts-theme.min.js

scripts-theme.min.js

558 ms

h1-slider-img-1.jpg

h1-slider-img-1.jpg

1112 ms

frontend.min.js

frontend.min.js

507 ms

script.min.js

script.min.js

498 ms

js_composer_front.min.js

js_composer_front.min.js

505 ms

counter.js

counter.js

528 ms

absoluteCounter.min.js

absoluteCounter.min.js

527 ms

font

font

194 ms

font

font

258 ms

button-script.js

button-script.js

521 ms

bartle-hall-logo.png

bartle-hall-logo.png

564 ms

Light@2x.png

Light@2x.png

519 ms

dummy.png

dummy.png

519 ms

JEBSON-scaled.jpg

JEBSON-scaled.jpg

953 ms

fa-brands-400.woff

fa-brands-400.woff

954 ms

Untitled-1.jpg

Untitled-1.jpg

971 ms

9-1-1-scaled.jpg

9-1-1-scaled.jpg

909 ms

JEB-scaled.jpg

JEB-scaled.jpg

916 ms

exclusively-yours-2.png

exclusively-yours-2.png

852 ms

JebsonPhoto-65-2-1-scaled.jpg

JebsonPhoto-65-2-1-scaled.jpg

1085 ms

landing-img-17.png

landing-img-17.png

845 ms

MorleyBartle471of1166-1.jpg

MorleyBartle471of1166-1.jpg

953 ms

doyle-81-1.jpg

doyle-81-1.jpg

824 ms

7794e33851f08eacc719aa59ac5b7070-xxlarge.jpg

7794e33851f08eacc719aa59ac5b7070-xxlarge.jpg

901 ms

Background.jpg

Background.jpg

868 ms

landing-img-18.png

landing-img-18.png

902 ms

h1-img-16.png

h1-img-16.png

916 ms

JEBSON-50-scaled.jpg

JEBSON-50-scaled.jpg

930 ms

recaptcha__en.js

recaptcha__en.js

22 ms

Accessibility Review

bartlehall.co.uk accessibility score

88

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

bartlehall.co.uk best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

bartlehall.co.uk SEO score

78

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

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

bartlehall.co.uk

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