Tools & Wizards About Us
holybushrestaurant.co.uk screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

holybushrestaurant.co.uk

Hollybush | Hollybush, Coventry, Coventry, Takeaway Order Online

Page Load Speed

7.8 sec in total

First Response

953 ms

Resources Loaded

6.4 sec

Page Rendered

444 ms

holybushrestaurant.co.uk screenshot

About Website

Visit holybushrestaurant.co.uk now to see the best up-to-date Holybushrestaurant content and also check out these interesting facts you probably never knew about holybushrestaurant.co.uk

They

Visit holybushrestaurant.co.uk

Key Findings

We analyzed Holybushrestaurant.co.uk page load time and found that the first response time was 953 ms and then it took 6.9 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

holybushrestaurant.co.uk performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value38.9 s

0/100

25%

SI (Speed Index)

Value18.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,090 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value1.915

0/100

15%

TTI (Time to Interactive)

Value35.4 s

0/100

10%

Network Requests Diagram

holybushrestaurant.co.uk

953 ms

component---src-pages-index-js.5e2a3565fa517e20aa6a.css

36 ms

styles.c75e88b4efec2fe9cbf4.css

60 ms

redircetion.js

81 ms

css

31 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 61% of them (35 requests) were addressed to the original Holybushrestaurant.co.uk, 21% (12 requests) were made to Public.touch2success.com and 7% (4 requests) were made to Nativesites.touch2success.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source 0bba85283010b328c484-f139c7401b3658260f434c192b129add.ssl.cf3.rackcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (26%)

Content Size

7.5 MB

After Optimization

5.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Holybushrestaurant.co.uk main page is 7.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 95.2 kB

  • Original 123.8 kB
  • After minification 122.1 kB
  • After compression 28.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 95.2 kB or 77% of the original size.

Image Optimization

-30%

Potential reduce by 1.8 MB

  • Original 6.0 MB
  • After minification 4.2 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. Obviously, Holybushrestaurant needs image optimization as it can save up to 1.8 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 587 B

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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

-0%

Potential reduce by 53 B

  • Original 85.9 kB
  • After minification 85.9 kB
  • After compression 85.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. Holybushrestaurant.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (52%)

Requests Now

46

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

holybushrestaurant.co.uk

holybushrestaurant.co.uk

953 ms

component---src-pages-index-js.5e2a3565fa517e20aa6a.css

component---src-pages-index-js.5e2a3565fa517e20aa6a.css

36 ms

styles.c75e88b4efec2fe9cbf4.css

styles.c75e88b4efec2fe9cbf4.css

60 ms

redircetion.js

redircetion.js

81 ms

css

css

31 ms

component---src-pages-index-js-707cbf39a7b5dd8b1020.js

component---src-pages-index-js-707cbf39a7b5dd8b1020.js

49 ms

069d7ed90813c7366736076cff52daac276ed88d-05ee27eda18db009d760.js

069d7ed90813c7366736076cff52daac276ed88d-05ee27eda18db009d760.js

78 ms

c7eb783b603a8af62b3aad0bbee176b1ac922daf-4e16324c62d92ea2b306.js

c7eb783b603a8af62b3aad0bbee176b1ac922daf-4e16324c62d92ea2b306.js

45 ms

4984e3ccc90976e5327b40b59feb43b8744b7015-eac7e442376b0971e333.js

4984e3ccc90976e5327b40b59feb43b8744b7015-eac7e442376b0971e333.js

149 ms

59179db633f39df00fe2a009fdbd4a1be77c3c04-33c3eb1929d420c2164f.js

59179db633f39df00fe2a009fdbd4a1be77c3c04-33c3eb1929d420c2164f.js

78 ms

19cb5c77716997e19d276ccefe7b7b6e60edb372-9b89b088f8d95d57070a.js

19cb5c77716997e19d276ccefe7b7b6e60edb372-9b89b088f8d95d57070a.js

78 ms

c742b37f598e800bb11992ac1e7d40e282dd4c48-8c20279210a7782448a0.js

c742b37f598e800bb11992ac1e7d40e282dd4c48-8c20279210a7782448a0.js

148 ms

23a316efa3e39be7b577d94b106f5bd58cbaf47e-9970cbdbbae6949f6014.js

23a316efa3e39be7b577d94b106f5bd58cbaf47e-9970cbdbbae6949f6014.js

158 ms

e66991c512f6962aab5cc85670e7f3006f83acab-22959a9439c6a22bc1bd.js

e66991c512f6962aab5cc85670e7f3006f83acab-22959a9439c6a22bc1bd.js

151 ms

02ef54e16e9962617397566e056b0c0f0bd31599-1de092e9db02f94d51c8.js

02ef54e16e9962617397566e056b0c0f0bd31599-1de092e9db02f94d51c8.js

149 ms

60ef815bac73872008e5b2fc235caee310b13a86-34a5ff3478f89b6fb7a7.js

60ef815bac73872008e5b2fc235caee310b13a86-34a5ff3478f89b6fb7a7.js

148 ms

2b03275895b99655fc7c9cd28667459d9fcd3bd2-070682bb0d4ee16392fc.js

2b03275895b99655fc7c9cd28667459d9fcd3bd2-070682bb0d4ee16392fc.js

152 ms

44cf4e6d4db1b22567d694ffeeae7f6c36ad8dad-b6c40d67f2351b1ca526.js

44cf4e6d4db1b22567d694ffeeae7f6c36ad8dad-b6c40d67f2351b1ca526.js

156 ms

8b92e626c21986eb7d0c7817f8d4c62fa600a872-9fbd262a5015b5285484.js

8b92e626c21986eb7d0c7817f8d4c62fa600a872-9fbd262a5015b5285484.js

156 ms

692547191e0ee956f56c2d4813724011d3c5f5c4-1059ba1c3f894210708c.js

692547191e0ee956f56c2d4813724011d3c5f5c4-1059ba1c3f894210708c.js

157 ms

b637e9a5-180782c9ae990907e0e7.js

b637e9a5-180782c9ae990907e0e7.js

157 ms

app-3738525ae83dbb9c039a.js

app-3738525ae83dbb9c039a.js

193 ms

d937cbbe-e2503ae5fb8007e3521d.js

d937cbbe-e2503ae5fb8007e3521d.js

207 ms

5a83d331-842ef41ccc47bed1d86a.js

5a83d331-842ef41ccc47bed1d86a.js

187 ms

64008582-48adfd47e89b1f995f02.js

64008582-48adfd47e89b1f995f02.js

192 ms

2852872c-5133bfd7798ee99130b4.js

2852872c-5133bfd7798ee99130b4.js

206 ms

styles-fe9c38ab7851d0a01fc2.js

styles-fe9c38ab7851d0a01fc2.js

226 ms

framework-5467bb6d9aec3c65dbef.js

framework-5467bb6d9aec3c65dbef.js

220 ms

webpack-runtime-68e63a7f1f47d1f363cc.js

webpack-runtime-68e63a7f1f47d1f363cc.js

227 ms

1571049367phpi0WNmF.jpg

1571049367phpi0WNmF.jpg

889 ms

1595950125phpZqYevp.png

1595950125phpZqYevp.png

126 ms

1593446639phpxSq93B.png

1593446639phpxSq93B.png

848 ms

php06f5sv.jpg

php06f5sv.jpg

487 ms

Appstore.svg

Appstore.svg

82 ms

gtm.js

gtm.js

70 ms

Playstore.svg

Playstore.svg

86 ms

Powered%20by-FH_white%20bg.png

Powered%20by-FH_white%20bg.png

144 ms

verified-by.svg

verified-by.svg

144 ms

phpmtULXs.png

phpmtULXs.png

5220 ms

1583913060phpGD0uzi.jpg

1583913060phpGD0uzi.jpg

1458 ms

1583913059phpWFHklN.png

1583913059phpWFHklN.png

1658 ms

1593696482phpzcY022.png

1593696482phpzcY022.png

1687 ms

php4cT0PU.jpg

php4cT0PU.jpg

1373 ms

1574203452phpZqRoSh.png

1574203452phpZqRoSh.png

1534 ms

phpKFmHsq.jpg

phpKFmHsq.jpg

1385 ms

phpErvp5V.jpg

phpErvp5V.jpg

1928 ms

1574203621phpadMirO.png

1574203621phpadMirO.png

2083 ms

phpHA2Ub4.png

phpHA2Ub4.png

2175 ms

phpIzUAAY.png

phpIzUAAY.png

1897 ms

phpcy6pdu.png

phpcy6pdu.png

2037 ms

Lato-Regular.woff

Lato-Regular.woff

32 ms

Lato-Medium.woff

Lato-Medium.woff

33 ms

Lato-Light.woff

Lato-Light.woff

57 ms

Lato-Semibold.woff

Lato-Semibold.woff

56 ms

Lato-Bold.woff

Lato-Bold.woff

27 ms

Lato-Black.woff

Lato-Black.woff

79 ms

Lato-Heavy.woff

Lato-Heavy.woff

56 ms

Accessibility Review

holybushrestaurant.co.uk accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

holybushrestaurant.co.uk SEO score

86

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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

holybushrestaurant.co.uk

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