Tools & Wizards About Us
nextlove.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

nextlove.com

An Online Dating Site for Divorced and Single Parents, Find your Next Love Online

Page Load Speed

3.7 sec in total

First Response

172 ms

Resources Loaded

2.4 sec

Page Rendered

1.2 sec

nextlove.com screenshot

About Website

Visit nextlove.com now to see the best up-to-date Next Love content for Sweden and also check out these interesting facts you probably never knew about nextlove.com

NextLove is Europe's leading Social Network for divorced and single parents that are looking to find new friends and their passion

Visit nextlove.com

Key Findings

We analyzed Nextlove.com page load time and found that the first response time was 172 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

nextlove.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

nextlove.com

172 ms

www.nextlove.com

644 ms

stylesheet.css

39 ms

styles.css

394 ms

lander-apr21.css

43 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Nextlove.com, 74% (45 requests) were made to D2h6lqdh1cfgdt.cloudfront.net and 5% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (925 ms) relates to the external source D2h6lqdh1cfgdt.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 293.9 kB (14%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nextlove.com main page is 2.0 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. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 44.0 kB

  • Original 52.0 kB
  • After minification 37.8 kB
  • After compression 8.0 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 14.1 kB, which is 27% 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 44.0 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 184.0 kB

  • Original 1.7 MB
  • After minification 1.5 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. Obviously, Next Love needs image optimization as it can save up to 184.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-7%

Potential reduce by 15.5 kB

  • Original 235.4 kB
  • After minification 235.4 kB
  • After compression 220.0 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

-84%

Potential reduce by 50.5 kB

  • Original 60.1 kB
  • After minification 49.6 kB
  • After compression 9.6 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. Nextlove.com needs all CSS files to be minified and compressed as it can save up to 50.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (18%)

Requests Now

44

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nextlove.com

nextlove.com

172 ms

www.nextlove.com

www.nextlove.com

644 ms

stylesheet.css

stylesheet.css

39 ms

styles.css

styles.css

394 ms

lander-apr21.css

lander-apr21.css

43 ms

lander-apr21.min.js

lander-apr21.min.js

41 ms

api.js

api.js

58 ms

gtm.js

gtm.js

244 ms

fbevents.js

fbevents.js

186 ms

header-desktop-bg.jpg

header-desktop-bg.jpg

155 ms

en.png

en.png

158 ms

dash.png

dash.png

159 ms

en.png

en.png

157 ms

nl-heart-orange.svg

nl-heart-orange.svg

207 ms

b-desktop.jpg

b-desktop.jpg

212 ms

track

track

691 ms

city

city

455 ms

a-1.svg

a-1.svg

72 ms

a-2.svg

a-2.svg

74 ms

a-3.svg

a-3.svg

71 ms

a-4.svg

a-4.svg

77 ms

c-1-2x.jpg

c-1-2x.jpg

106 ms

d-1-2x.png

d-1-2x.png

116 ms

d-2-2x.jpg

d-2-2x.jpg

78 ms

d-3-2x.jpg

d-3-2x.jpg

107 ms

f-1-2x.jpg

f-1-2x.jpg

106 ms

g-1.svg

g-1.svg

110 ms

g-2.svg

g-2.svg

113 ms

g-3.svg

g-3.svg

112 ms

h-1-2x.jpg

h-1-2x.jpg

116 ms

h-2-2x.jpg

h-2-2x.jpg

115 ms

h-3-2x.jpg

h-3-2x.jpg

201 ms

i-desktop-2x.jpg

i-desktop-2x.jpg

121 ms

app-store-black.png

app-store-black.png

117 ms

google-play-black.png

google-play-black.png

117 ms

security-gray-2x.png

security-gray-2x.png

118 ms

ios.png

ios.png

400 ms

app-store-dec21.png

app-store-dec21.png

120 ms

android.png

android.png

424 ms

google-play-dec21.png

google-play-dec21.png

420 ms

e-1.jpg

e-1.jpg

579 ms

recaptcha__en.js

recaptcha__en.js

121 ms

GothamNarrow-Book.ttf

GothamNarrow-Book.ttf

190 ms

GothamNarrow-Black.ttf

GothamNarrow-Black.ttf

191 ms

GothamNarrow-Medium.ttf

GothamNarrow-Medium.ttf

192 ms

GothamNarrow-Light.ttf

GothamNarrow-Light.ttf

191 ms

GothamNarrow-Thin.ttf

GothamNarrow-Thin.ttf

193 ms

GothamNarrow-Bold.ttf

GothamNarrow-Bold.ttf

192 ms

GothamNarrow-BoldItalic.ttf

GothamNarrow-BoldItalic.ttf

655 ms

victoriamilan.woff

victoriamilan.woff

212 ms

GothamNarrow-BlackItalic.ttf

GothamNarrow-BlackItalic.ttf

597 ms

GothamNarrow-MediumItalic.ttf

GothamNarrow-MediumItalic.ttf

925 ms

GothamNarrow-BookItalic.ttf

GothamNarrow-BookItalic.ttf

380 ms

GothamNarrow-LightItalic.ttf

GothamNarrow-LightItalic.ttf

901 ms

GothamNarrow-ThinItalic.ttf

GothamNarrow-ThinItalic.ttf

915 ms

fallback

fallback

58 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

35 ms

logo_48.png

logo_48.png

3 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

18 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

27 ms

Accessibility Review

nextlove.com accessibility score

76

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

Links do not have a discernible name

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

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

SEO Factors

nextlove.com SEO score

100

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

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

nextlove.com

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