Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

Page Load Speed

10 sec in total

First Response

1.3 sec

Resources Loaded

8.6 sec

Page Rendered

118 ms

flove.com screenshot

About Website

Click here to check amazing Flove content. Otherwise, check out these important facts you probably never knew about flove.com

Visit flove.com

Key Findings

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

Performance Metrics

flove.com performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

flove.com

1251 ms

jquery.js

4303 ms

stat.php

1639 ms

welcome.gif

1092 ms

backimg.jpg

1456 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original Flove.com, 27% (3 requests) were made to 4.cn and 9% (1 request) were made to Libs.baidu.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Libs.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 51.6 kB (50%)

Content Size

102.7 kB

After Optimization

51.2 kB

In fact, the total size of Flove.com main page is 102.7 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. Only 5% of websites need less resources to load. Javascripts take 92.2 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 4.3 kB

  • Original 6.7 kB
  • After minification 5.6 kB
  • After compression 2.4 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 1.1 kB, which is 17% 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 4.3 kB or 65% of the original size.

Image Optimization

-0%

Potential reduce by 18 B

  • Original 3.8 kB
  • After minification 3.7 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. Flove images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 47.2 kB

  • Original 92.2 kB
  • After minification 92.2 kB
  • After compression 45.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 47.2 kB or 51% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flove. According to our analytics all requests are already optimized.

Accessibility Review

flove.com accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

High

Page has valid source maps

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flove.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 Flove.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 description is not detected on the main page of Flove. 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: