Tools & Wizards About Us
lovehearts.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lovehearts.com

Default Web Site Page

Page Load Speed

2 sec in total

First Response

382 ms

Resources Loaded

1.2 sec

Page Rendered

349 ms

lovehearts.com screenshot

About Website

Welcome to lovehearts.com homepage info - get ready to check Lovehearts best content for United Kingdom right away, or after learning these important things about lovehearts.com

Welcome to the Love Hearts homepage by Swizzels Matlow.

Visit lovehearts.com

Key Findings

We analyzed Lovehearts.com page load time and found that the first response time was 382 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

lovehearts.com performance score

0

Network Requests Diagram

lovehearts.com

382 ms

jquery-1.10.1.min.js

13 ms

jquery.prettyPhoto.js

35 ms

prettyPhoto.css

33 ms

css

38 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 69% of them (22 requests) were addressed to the original Lovehearts.com, 13% (4 requests) were made to Google-analytics.com and 6% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (710 ms) belongs to the original domain Lovehearts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.5 kB (19%)

Content Size

952.6 kB

After Optimization

770.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lovehearts.com main page is 952.6 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. 35% of websites need less resources to load. Images take 880.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 8.4 kB

  • Original 10.7 kB
  • After minification 7.3 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 32% 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 8.4 kB or 79% of the original size.

Image Optimization

-16%

Potential reduce by 141.5 kB

  • Original 880.3 kB
  • After minification 738.8 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. Obviously, Lovehearts needs image optimization as it can save up to 141.5 kB or 16% 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 70 B

  • Original 21.7 kB
  • After minification 21.7 kB
  • After compression 21.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

-81%

Potential reduce by 32.6 kB

  • Original 40.0 kB
  • After minification 36.5 kB
  • After compression 7.4 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. Lovehearts.com needs all CSS files to be minified and compressed as it can save up to 32.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (21%)

Requests Now

29

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lovehearts.com

lovehearts.com

382 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

13 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

35 ms

prettyPhoto.css

prettyPhoto.css

33 ms

css

css

38 ms

main.css

main.css

154 ms

home.css

home.css

160 ms

bg_dots.jpg

bg_dots.jpg

159 ms

analytics.js

analytics.js

65 ms

logo_2015.png

logo_2015.png

159 ms

home.png

home.png

94 ms

one-direction.png

one-direction.png

81 ms

play.png

play.png

162 ms

win.png

win.png

162 ms

shop.png

shop.png

159 ms

swizzels.png

swizzels.png

236 ms

facebook.png

facebook.png

179 ms

twitter.png

twitter.png

234 ms

register.png

register.png

237 ms

shop.png

shop.png

238 ms

top_bg.gif

top_bg.gif

237 ms

shop-graphic-2016-feb.png

shop-graphic-2016-feb.png

652 ms

lovehearts-story-60-years-of-love-button.png

lovehearts-story-60-years-of-love-button.png

551 ms

shop-graphic-sweet-memories1.png

shop-graphic-sweet-memories1.png

710 ms

bottom_play.png

bottom_play.png

315 ms

factory-of-love-banner.png

factory-of-love-banner.png

710 ms

love-calculator-banner.png

love-calculator-banner.png

552 ms

obisuY-MenYRAFwd-r2NhfesZW2xOQ-xsNqO47m55DA.ttf

obisuY-MenYRAFwd-r2NhfesZW2xOQ-xsNqO47m55DA.ttf

26 ms

SL0aFUFfkFMMdariYQ3_YZ0EAVxt0G0biEntp43Qt6E.ttf

SL0aFUFfkFMMdariYQ3_YZ0EAVxt0G0biEntp43Qt6E.ttf

27 ms

ecommerce.js

ecommerce.js

18 ms

collect

collect

12 ms

collect

collect

15 ms

SEO Factors

lovehearts.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lovehearts.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lovehearts.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

lovehearts.com

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