Tools & Wizards About Us
wetrip.fr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wetrip.fr

Wetrip - Allons-y !

Page Load Speed

3 sec in total

First Response

241 ms

Resources Loaded

2 sec

Page Rendered

743 ms

wetrip.fr screenshot

About Website

Visit wetrip.fr now to see the best up-to-date Wetrip content and also check out these interesting facts you probably never knew about wetrip.fr

Faites vos comptes entre amis après un voyage en voiture avec notre application

Visit wetrip.fr

Key Findings

We analyzed Wetrip.fr page load time and found that the first response time was 241 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

wetrip.fr performance score

0

Network Requests Diagram

wetrip.fr

241 ms

accueil

131 ms

maxresdefault.jpg

154 ms

lander.css

83 ms

font-awesome.css

43 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Wetrip.fr, 32% (22 requests) were made to Static.xx.fbcdn.net and 9% (6 requests) were made to Images.clickfunnels.com. The less responsive or slowest element that took the longest time to load (714 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

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

Content Size

1.9 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wetrip.fr main page is 1.9 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. 85% 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. Javascripts take 827.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 79.7 kB

  • Original 93.7 kB
  • After minification 92.2 kB
  • After compression 14.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. 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 79.7 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 713 B

  • Original 679.0 kB
  • After minification 678.3 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. Wetrip images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 550.6 kB

  • Original 827.1 kB
  • After minification 826.9 kB
  • After compression 276.5 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 550.6 kB or 67% of the original size.

CSS Optimization

-66%

Potential reduce by 228.9 kB

  • Original 348.8 kB
  • After minification 343.2 kB
  • After compression 119.9 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. Wetrip.fr needs all CSS files to be minified and compressed as it can save up to 228.9 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (69%)

Requests Now

59

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wetrip.fr

wetrip.fr

241 ms

accueil

accueil

131 ms

maxresdefault.jpg

maxresdefault.jpg

154 ms

lander.css

lander.css

83 ms

font-awesome.css

font-awesome.css

43 ms

css

css

66 ms

lander.js

lander.js

134 ms

analytics.js

analytics.js

427 ms

closemodal.png

closemodal.png

538 ms

logo-horizontal-blanc.png

logo-horizontal-blanc.png

574 ms

comments.php

comments.php

714 ms

sdk.js

sdk.js

550 ms

maddyness.png

maddyness.png

627 ms

logo-jmlesstartups-gris.png

logo-jmlesstartups-gris.png

607 ms

infographie2.png

infographie2.png

662 ms

blank-phone.png

blank-phone.png

652 ms

infographie-wetrip.png

infographie-wetrip.png

697 ms

fql

fql

487 ms

iframe_api

iframe_api

361 ms

widgets.js

widgets.js

378 ms

widgets.js

widgets.js

441 ms

widgets.js

widgets.js

474 ms

617 ms

__utm.gif

__utm.gif

195 ms

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

269 ms

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

287 ms

JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf

JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf

305 ms

UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf

UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf

358 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

159 ms

1g0svRuZGFwAB9MiuAAAAA==

1g0svRuZGFwAB9MiuAAAAA==

1 ms

collect

collect

119 ms

cf.js

cf.js

30 ms

144 ms

xd_arbiter.php

xd_arbiter.php

107 ms

www-widgetapi.js

www-widgetapi.js

85 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

88 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

95 ms

yBwS6rJyogl.css

yBwS6rJyogl.css

102 ms

ZeuPykSxSED.css

ZeuPykSxSED.css

105 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

120 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

119 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

119 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

156 ms

1FCa-btixu2.js

1FCa-btixu2.js

181 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

192 ms

FyxLoiww5bU.js

FyxLoiww5bU.js

191 ms

HaMjR2eXz4B.js

HaMjR2eXz4B.js

205 ms

WN2wSsLOuKy.js

WN2wSsLOuKy.js

211 ms

Kt4tkgSRvHH.js

Kt4tkgSRvHH.js

224 ms

Q4A0UyjU8W2.js

Q4A0UyjU8W2.js

218 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

231 ms

tweet.2c548e167cf5bdb0bd941e41896f257d.js

tweet.2c548e167cf5bdb0bd941e41896f257d.js

214 ms

-gW1tV4wrtA

-gW1tV4wrtA

175 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

191 ms

www-embed-player.js

www-embed-player.js

311 ms

base.js

base.js

354 ms

odA9sNLrE86.jpg

odA9sNLrE86.jpg

178 ms

fav.png

fav.png

177 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

134 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

132 ms

syndication

syndication

291 ms

tweets.json

tweets.json

290 ms

eR-qA8bp1RM.js

eR-qA8bp1RM.js

185 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

184 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

183 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

90 ms

ad_status.js

ad_status.js

92 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

42 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

43 ms

SEO Factors

wetrip.fr SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wetrip.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Wetrip.fr 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

wetrip.fr

Open Graph data is detected on the main page of Wetrip. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: