Tools & Wizards About Us
yeotownkitchen.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

yeotownkitchen.com

Yeotown Restaurants London

Page Load Speed

8.2 sec in total

First Response

1.3 sec

Resources Loaded

6.6 sec

Page Rendered

325 ms

yeotownkitchen.com screenshot

About Website

Click here to check amazing Yeotown Kitchen content. Otherwise, check out these important facts you probably never knew about yeotownkitchen.com

Yeotown London offers up California inspired healthy, wholesome, colourful dishes with a spoonful of British sensibility.

Visit yeotownkitchen.com

Key Findings

We analyzed Yeotownkitchen.com page load time and found that the first response time was 1.3 sec 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

yeotownkitchen.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value700 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

1300 ms

canvas.css

220 ms

powerkit.css

403 ms

style.min.css

620 ms

block.css

327 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yeotownkitchen.com, 4% (5 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Yeotown.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (29%)

Content Size

5.4 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yeotownkitchen.com main page is 5.4 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. 55% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 138.5 kB

  • Original 159.9 kB
  • After minification 156.9 kB
  • After compression 21.4 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 138.5 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 136.0 kB

  • Original 3.4 MB
  • After minification 3.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. Yeotown Kitchen images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 383.5 kB

  • Original 838.8 kB
  • After minification 807.3 kB
  • After compression 455.3 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 383.5 kB or 46% of the original size.

CSS Optimization

-88%

Potential reduce by 920.8 kB

  • Original 1.0 MB
  • After minification 940.3 kB
  • After compression 124.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. Yeotownkitchen.com needs all CSS files to be minified and compressed as it can save up to 920.8 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 91 (86%)

Requests Now

106

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1300 ms

canvas.css

canvas.css

220 ms

powerkit.css

powerkit.css

403 ms

style.min.css

style.min.css

620 ms

block.css

block.css

327 ms

block.css

block.css

394 ms

block.css

block.css

396 ms

block.css

block.css

408 ms

block.css

block.css

471 ms

block-row.css

block-row.css

499 ms

block-posts.css

block-posts.css

513 ms

block-justified-gallery.css

block-justified-gallery.css

505 ms

block-slider-gallery.css

block-slider-gallery.css

516 ms

block-posts-sidebar.css

block-posts-sidebar.css

592 ms

posts-sidebar.css

posts-sidebar.css

606 ms

twitter-slider.css

twitter-slider.css

609 ms

tiles.css

tiles.css

623 ms

horizontal-tiles.css

horizontal-tiles.css

625 ms

full.css

full.css

703 ms

slider.css

slider.css

731 ms

carousel.css

carousel.css

716 ms

wide.css

wide.css

738 ms

narrow.css

narrow.css

737 ms

advanced-popups-public.css

advanced-popups-public.css

754 ms

block.css

block.css

811 ms

block.css

block.css

822 ms

block.css

block.css

839 ms

block.css

block.css

842 ms

block.css

block.css

848 ms

block.css

block.css

862 ms

styles.css

styles.css

917 ms

public-powerkit-author-box.css

public-powerkit-author-box.css

927 ms

public-powerkit-basic-elements.css

public-powerkit-basic-elements.css

984 ms

public-powerkit-content-formatting.css

public-powerkit-content-formatting.css

968 ms

public-powerkit-contributors.css

public-powerkit-contributors.css

957 ms

public-powerkit-featured-categories.css

public-powerkit-featured-categories.css

973 ms

api.js

api.js

36 ms

public-powerkit-inline-posts.css

public-powerkit-inline-posts.css

959 ms

public-powerkit-justified-gallery.css

public-powerkit-justified-gallery.css

817 ms

glightbox.min.css

glightbox.min.css

760 ms

public-powerkit-lightbox.css

public-powerkit-lightbox.css

685 ms

public-powerkit-opt-in-forms.css

public-powerkit-opt-in-forms.css

695 ms

public-powerkit-scroll-to-top.css

public-powerkit-scroll-to-top.css

695 ms

public-powerkit-social-links.css

public-powerkit-social-links.css

956 ms

public-powerkit-table-of-contents.css

public-powerkit-table-of-contents.css

669 ms

public-powerkit-widget-about.css

public-powerkit-widget-about.css

693 ms

frontend.min.css

frontend.min.css

904 ms

jquery-ui.css

jquery-ui.css

743 ms

jquery.timepicker.min.css

jquery.timepicker.min.css

689 ms

wpem-grid.min.css

wpem-grid.min.css

776 ms

style.css

style.css

749 ms

style.css

style.css

1131 ms

style.css

style.css

751 ms

style.css

style.css

868 ms

jquery.min.js

jquery.min.js

888 ms

jquery-migrate.min.js

jquery-migrate.min.js

777 ms

advanced-popups-public.js

advanced-popups-public.js

781 ms

public-block-alert.js

public-block-alert.js

786 ms

public-block-collapsibles.js

public-block-collapsibles.js

844 ms

public-block-tabs.js

public-block-tabs.js

858 ms

colcade.js

colcade.js

864 ms

public-block-posts.js

public-block-posts.js

807 ms

jquery.justifiedGallery.min.js

jquery.justifiedGallery.min.js

811 ms

public-block-justified-gallery.js

public-block-justified-gallery.js

845 ms

imagesloaded.min.js

imagesloaded.min.js

865 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

994 ms

public-block-slider-gallery.js

public-block-slider-gallery.js

862 ms

index.js

index.js

908 ms

index.js

index.js

901 ms

public-powerkit-basic-elements.js

public-powerkit-basic-elements.js

870 ms

public-powerkit-justified-gallery.js

public-powerkit-justified-gallery.js

865 ms

glightbox.min.js

glightbox.min.js

904 ms

public-powerkit-lightbox.js

public-powerkit-lightbox.js

893 ms

public-powerkit-opt-in-forms.js

public-powerkit-opt-in-forms.js

903 ms

public-powerkit-scroll-to-top.js

public-powerkit-scroll-to-top.js

900 ms

public-powerkit-table-of-contents.js

public-powerkit-table-of-contents.js

867 ms

common.min.js

common.min.js

869 ms

core.min.js

core.min.js

903 ms

jquery.timepicker.min.js

jquery.timepicker.min.js

905 ms

owl.carousel.min.js

owl.carousel.min.js

933 ms

ofi.min.js

ofi.min.js

862 ms

jarallax.min.js

jarallax.min.js

867 ms

jarallax-video.min.js

jarallax-video.min.js

816 ms

scripts.js

scripts.js

768 ms

script.min.js

script.min.js

750 ms

wp-polyfill.min.js

wp-polyfill.min.js

851 ms

index.js

index.js

811 ms

custom.js

custom.js

773 ms

css2

css2

29 ms

embed

embed

186 ms

embed

embed

219 ms

yeotown_logo_y.png

yeotown_logo_y.png

394 ms

yeotown_logo_only_yellow.png

yeotown_logo_only_yellow.png

464 ms

Yeotown-Restaurants-London.jpeg

Yeotown-Restaurants-London.jpeg

464 ms

YEO231-1160x774-1.jpg

YEO231-1160x774-1.jpg

599 ms

YEO250-1160x774-1.jpg

YEO250-1160x774-1.jpg

762 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

474 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

509 ms

S6uyw4BMUTPHvxk.ttf

S6uyw4BMUTPHvxk.ttf

22 ms

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

517 ms

S6u9w4BMUTPHh7USSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh7USSwaPHw3q5d0N7w.woff

532 ms

S6u9w4BMUTPHh7USew8.ttf

S6u9w4BMUTPHh7USew8.ttf

31 ms

S6u8w4BMUTPHh30wWw.ttf

S6u8w4BMUTPHh30wWw.ttf

56 ms

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

593 ms

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

624 ms

S6u9w4BMUTPHh6UVew8.ttf

S6u9w4BMUTPHh6UVew8.ttf

65 ms

S6u9w4BMUTPHh50Xew8.ttf

S6u9w4BMUTPHh50Xew8.ttf

66 ms

icons.ttf

icons.ttf

633 ms

powerkit-icons.woff

powerkit-icons.woff

644 ms

js

js

38 ms

search.js

search.js

5 ms

geometry.js

geometry.js

7 ms

main.js

main.js

14 ms

recaptcha__en.js

recaptcha__en.js

22 ms

Achada_do_Gramacho_seascape_Simon-Zino-min.jpg

Achada_do_Gramacho_seascape_Simon-Zino-min.jpg

441 ms

Screen-Shot-2020-11-14-at-22.26.56-min2.jpg

Screen-Shot-2020-11-14-at-22.26.56-min2.jpg

727 ms

yeotownkitchen_093017_gh004.jpg

yeotownkitchen_093017_gh004.jpg

716 ms

madeira_google_map.png

madeira_google_map.png

385 ms

devon_google_map.png

devon_google_map.png

441 ms

london_google_map.png

london_google_map.png

584 ms

powerkit-icons.woff

powerkit-icons.woff

111 ms

Accessibility Review

yeotownkitchen.com accessibility score

85

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

<frame> or <iframe> elements do not have a title

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.

Best Practices

yeotownkitchen.com 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

yeotownkitchen.com SEO score

98

Search Engine Optimization Advices

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

yeotownkitchen.com

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