Tools & Wizards About Us
lover.ly screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

lover.ly

Loverly: The Free Online Wedding Planner Website

Page Load Speed

1.5 sec in total

First Response

125 ms

Resources Loaded

1.1 sec

Page Rendered

349 ms

lover.ly screenshot

About Website

Visit lover.ly now to see the best up-to-date Lover content for United States and also check out these interesting facts you probably never knew about lover.ly

Loverly is the ultimate do it yourself event planning platform. We make it easy to plan events with a FREE wedding planning checklist, guest list manager, wedding budget tool, vendor manager, vision b...

Visit lover.ly

Key Findings

We analyzed Lover.ly page load time and found that the first response time was 125 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

lover.ly performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value1,800 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.056

98/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

lover.ly

125 ms

global.css

7 ms

section.home.css

25 ms

global.js

41 ms

section.home.js

40 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 25% of them (6 requests) were addressed to the original Lover.ly, 42% (10 requests) were made to A.lover.ly and 8% (2 requests) were made to Gtrk.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (729 ms) relates to the external source Tag.bounceexchange.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 992.7 kB (48%)

Content Size

2.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lover.ly main page is 2.1 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. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 48.3 kB

  • Original 68.5 kB
  • After minification 65.9 kB
  • After compression 20.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 48.3 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 47.5 kB

  • Original 718.9 kB
  • After minification 671.4 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. Lover images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 897.0 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 379.2 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 897.0 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (37%)

Requests Now

19

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lover.ly

lover.ly

125 ms

global.css

global.css

7 ms

section.home.css

section.home.css

25 ms

global.js

global.js

41 ms

section.home.js

section.home.js

40 ms

gtm.js

gtm.js

81 ms

homepage-left.jpg

homepage-left.jpg

160 ms

homepage-right-0.jpg

homepage-right-0.jpg

132 ms

homepage-right-1.jpg

homepage-right-1.jpg

85 ms

quote-background.jpg

quote-background.jpg

113 ms

apple-store-badge.png

apple-store-badge.png

73 ms

google-store-badge.png

google-store-badge.png

73 ms

global_sprite_3.0.png

global_sprite_3.0.png

23 ms

Roboto-Light-webfont.woff

Roboto-Light-webfont.woff

130 ms

RobotoCondensed-Bold-webfont.woff

RobotoCondensed-Bold-webfont.woff

94 ms

DroidSerif-Regular-webfont.woff

DroidSerif-Regular-webfont.woff

131 ms

Roboto-Medium-webfont.woff

Roboto-Medium-webfont.woff

125 ms

conversion_async.js

conversion_async.js

151 ms

addthis_widget.js

addthis_widget.js

149 ms

480827.js

480827.js

286 ms

i.js

i.js

729 ms

7507.js

7507.js

191 ms

s

s

56 ms

u

u

38 ms

Accessibility Review

lover.ly accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Best Practices

lover.ly best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

lover.ly SEO score

81

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lover.ly 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 Lover.ly 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

lover.ly

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