Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

love-struck.com

Love Struck | Healthy Frozen Smoothie Packs & Mixes Delivery UK

Page Load Speed

2.8 sec in total

First Response

76 ms

Resources Loaded

766 ms

Page Rendered

2 sec

About Website

Welcome to love-struck.com homepage info - get ready to check Love Struck best content right away, or after learning these important things about love-struck.com

Healthy smoothies, shakes & soups. Create your favourite blends in an instant with our pre-packaged frozen smoothie mixes for the UK. Buy now.

Visit love-struck.com

Key Findings

We analyzed Love-struck.com page load time and found that the first response time was 76 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

love-struck.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value6,460 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

love-struck.com

76 ms

index.css

74 ms

public-modern.css

60 ms

mediaelementplayer-legacy.min.css

39 ms

wp-mediaelement.min.css

58 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 74% of them (85 requests) were addressed to the original Love-struck.com, 4% (5 requests) were made to Cdn.jsdelivr.net and 3% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (338 ms) relates to the external source Cdn-4.convertexperiments.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 901.2 kB (61%)

Content Size

1.5 MB

After Optimization

584.8 kB

In fact, the total size of Love-struck.com main page is 1.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. HTML takes 931.8 kB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 886.7 kB

  • Original 931.8 kB
  • After minification 810.6 kB
  • After compression 45.1 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. This page needs HTML code to be minified as it can gain 121.2 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 886.7 kB or 95% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 12.6 kB
  • After minification 12.6 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. Love Struck images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.5 kB

  • Original 312.2 kB
  • After minification 312.2 kB
  • After compression 304.7 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

-3%

Potential reduce by 7.1 kB

  • Original 229.5 kB
  • After minification 229.5 kB
  • After compression 222.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. Love-struck.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 96 (89%)

Requests Now

108

After Optimization

12

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

Accessibility Review

love-struck.com accessibility score

87

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

love-struck.com 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

High

Page has valid source maps

SEO Factors

love-struck.com SEO score

83

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

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 Love-struck.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 Love-struck.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

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