Tools & Wizards About Us
fivory.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fivory.com

Lyf Pay, l'application qui incarne le paiement d'aujourd'hui

Page Load Speed

8.5 sec in total

First Response

318 ms

Resources Loaded

7.5 sec

Page Rendered

674 ms

fivory.com screenshot

About Website

Click here to check amazing Fivory content for France. Otherwise, check out these important facts you probably never knew about fivory.com

Découvrez Lyf Pay, l'application qui regroupe paiement mobile, entre amis, cagnottes, dons et offres exclusives ! Lyf Pay, le paiement d'aujourd'hui !

Visit fivory.com

Key Findings

We analyzed Fivory.com page load time and found that the first response time was 318 ms and then it took 8.2 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

fivory.com performance score

0

Network Requests Diagram

fivory.com

318 ms

3422 ms

cssLoadAsync.js

101 ms

tracking.js

230 ms

widgets.js

26 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 59% of them (54 requests) were addressed to the original Fivory.com, 8% (7 requests) were made to Pixel.mathtag.com and 3% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Fivory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 627.5 kB (44%)

Content Size

1.4 MB

After Optimization

805.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 73.4 kB

  • Original 89.2 kB
  • After minification 69.0 kB
  • After compression 15.8 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 20.2 kB, which is 23% 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 73.4 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 2.6 kB

  • Original 564.1 kB
  • After minification 561.5 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. Fivory images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 196.6 kB

  • Original 357.9 kB
  • After minification 355.3 kB
  • After compression 161.3 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 196.6 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 354.9 kB

  • Original 421.7 kB
  • After minification 416.2 kB
  • After compression 66.8 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. Fivory.com needs all CSS files to be minified and compressed as it can save up to 354.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (49%)

Requests Now

86

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fivory.com

fivory.com

318 ms

3422 ms

cssLoadAsync.js

cssLoadAsync.js

101 ms

tracking.js

tracking.js

230 ms

widgets.js

widgets.js

26 ms

require.min.js

require.min.js

44 ms

%7B%7BidYoutube%7D%7D

%7B%7BidYoutube%7D%7D

90 ms

main.js

main.js

267 ms

www-embed-player-vfl-z2BtK.css

www-embed-player-vfl-z2BtK.css

15 ms

www-embed-player.js

www-embed-player.js

33 ms

base.js

base.js

57 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

43 ms

ad_status.js

ad_status.js

49 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

617 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

649 ms

ga.js

ga.js

64 ms

gtm.js

gtm.js

118 ms

fbds.js

fbds.js

204 ms

__utm.gif

__utm.gif

12 ms

app.min.css

app.min.css

201 ms

jquery.min.js

jquery.min.js

24 ms

angular.min.js

angular.min.js

49 ms

collect

collect

64 ms

analytics.js

analytics.js

27 ms

a.js;m=11007201904321;cache=0.5494377112481743

a.js;m=11007201904321;cache=0.5494377112481743

46 ms

fbevents.js

fbevents.js

104 ms

libs-angular.min.js

libs-angular.min.js

497 ms

app.min.js

app.min.js

362 ms

collect

collect

4 ms

collect

collect

15 ms

conversion.js

conversion.js

28 ms

19 ms

35 ms

8 ms

15 ms

js

js

53 ms

i.js

i.js

160 ms

gentona-light.woff

gentona-light.woff

207 ms

gentona-book.woff

gentona-book.woff

285 ms

gentona-extralight.woff

gentona-extralight.woff

399 ms

js

js

23 ms

img

img

30 ms

iframe

iframe

32 ms

img

img

28 ms

img

img

21 ms

lang.json

lang.json

103 ms

dayTime.json

dayTime.json

100 ms

videos.json

videos.json

118 ms

logo_fb.svg

logo_fb.svg

119 ms

logo_tw.svg

logo_tw.svg

102 ms

close.svg

close.svg

158 ms

logo_apple.svg

logo_apple.svg

165 ms

logo_android.svg

logo_android.svg

173 ms

burger.json

burger.json

181 ms

__utm.gif

__utm.gif

35 ms

consumerIndex.json

consumerIndex.json

206 ms

collect

collect

6 ms

logoTop.png

logoTop.png

386 ms

partners.json

partners.json

152 ms

consumerFivoryBenefits.json

consumerFivoryBenefits.json

143 ms

testimonies.json

testimonies.json

168 ms

bt_play.svg

bt_play.svg

105 ms

color_ic_dropdown.svg

color_ic_dropdown.svg

101 ms

logo_fb.png

logo_fb.png

107 ms

logo_twitter.png

logo_twitter.png

108 ms

logo_fivory.svg

logo_fivory.svg

103 ms

reddot.png

reddot.png

97 ms

blank.png

blank.png

177 ms

twitter.png

twitter.png

176 ms

facebook.png

facebook.png

185 ms

default.jpg

default.jpg

202 ms

check.png

check.png

211 ms

preview2.jpg

preview2.jpg

851 ms

bg_title_benefits_green.png

bg_title_benefits_green.png

274 ms

bg_title_news_green.png

bg_title_news_green.png

280 ms

news_picto_vert.svg

news_picto_vert.svg

276 ms

bg_title_offers_green.png

bg_title_offers_green.png

303 ms

offers_picto_vert.svg

offers_picto_vert.svg

317 ms

bg_title_testimonies.png

bg_title_testimonies.png

371 ms

bg_title_find_green.png

bg_title_find_green.png

367 ms

color_ic_dropdown.svg

color_ic_dropdown.svg

375 ms

bg_title_newsletter.png

bg_title_newsletter.png

403 ms

dot.svg

dot.svg

375 ms

B2C_2.jpg

B2C_2.jpg

630 ms

B2C_1.jpg

B2C_1.jpg

515 ms

partnersSprite.png

partnersSprite.png

711 ms

B2C1_payer.jpg

B2C1_payer.jpg

643 ms

B2C2_follow.jpg

B2C2_follow.jpg

572 ms

B2C3_loyalty.jpg

B2C3_loyalty.jpg

604 ms

B2C4_depenses.jpg

B2C4_depenses.jpg

784 ms

pixel

pixel

25 ms

img

img

30 ms

SEO Factors

fivory.com SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fivory.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Fivory.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

fivory.com

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