Tools & Wizards About Us
gettasty.co.uk screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

gettasty.co.uk

Get Tasty

Page Load Speed

1.6 sec in total

First Response

447 ms

Resources Loaded

1 sec

Page Rendered

132 ms

gettasty.co.uk screenshot

About Website

Click here to check amazing Get Tasty content. Otherwise, check out these important facts you probably never knew about gettasty.co.uk

Get Tasty

Visit gettasty.co.uk

Key Findings

We analyzed Gettasty.co.uk page load time and found that the first response time was 447 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

gettasty.co.uk performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value66.2 s

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value10,920 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value31.4 s

0/100

10%

Network Requests Diagram

www.gettasty.com

447 ms

css2

59 ms

style.css

121 ms

index.min.js

225 ms

firebase-app.js

44 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Gettasty.co.uk, 29% (6 requests) were made to Gstatic.com and 24% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (484 ms) relates to the external source Gettasty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.6 kB (24%)

Content Size

10.8 kB

After Optimization

8.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Gettasty.co.uk main page is 10.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 6.9 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 2.0 kB

  • Original 3.3 kB
  • After minification 3.3 kB
  • After compression 1.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 2.0 kB or 60% of the original size.

Image Optimization

-9%

Potential reduce by 625 B

  • Original 6.9 kB
  • After minification 6.3 kB

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. Get Tasty images are well optimized though.

CSS Optimization

-2%

Potential reduce by 9 B

  • Original 555 B
  • After minification 555 B
  • After compression 546 B

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. Gettasty.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (71%)

Requests Now

14

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.gettasty.com

www.gettasty.com

447 ms

css2

css2

59 ms

style.css

style.css

121 ms

index.min.js

index.min.js

225 ms

firebase-app.js

firebase-app.js

44 ms

firebase-messaging.js

firebase-messaging.js

54 ms

firebase-auth.js

firebase-auth.js

63 ms

firebase-analytics.js

firebase-analytics.js

61 ms

firebase-database.js

firebase-database.js

65 ms

google-pay.js

google-pay.js

153 ms

my-apple-pay.js

my-apple-pay.js

128 ms

firebase-firestore.js

firebase-firestore.js

63 ms

jsQr.js

jsQr.js

177 ms

main.dart.js

main.dart.js

484 ms

gt_on_black.png

gt_on_black.png

104 ms

index.min.js

index.min.js

116 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

149 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff

150 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff

155 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff

158 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff

159 ms

Accessibility Review

gettasty.co.uk accessibility score

85

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

gettasty.co.uk best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Requests the notification permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

gettasty.co.uk SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gettasty.co.uk can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Gettasty.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

gettasty.co.uk

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