Tools & Wizards About Us
paris.voisineo.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

paris.voisineo.com

Voisineo Paris - Rencontres amicales entre Voisins à Paris

Page Load Speed

2.3 sec in total

First Response

349 ms

Resources Loaded

1.7 sec

Page Rendered

210 ms

paris.voisineo.com screenshot

About Website

Visit paris.voisineo.com now to see the best up-to-date Paris Voisineo content for France and also check out these interesting facts you probably never knew about paris.voisineo.com

Voisineo est un lieu de rencontre local avec vos voisins, votre quartier, vos commerces de proximité à Paris

Visit paris.voisineo.com

Key Findings

We analyzed Paris.voisineo.com page load time and found that the first response time was 349 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

paris.voisineo.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.109

87/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

paris.voisineo.com

349 ms

jquery-1.2.6.pack.js

242 ms

global-1-1.css

165 ms

menu.js

167 ms

fonctions.js

168 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 45% of them (37 requests) were addressed to the original Paris.voisineo.com, 46% (38 requests) were made to Voisineo.com and 4% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (960 ms) belongs to the original domain Paris.voisineo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.8 kB (13%)

Content Size

465.4 kB

After Optimization

402.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Paris.voisineo.com main page is 465.4 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. 25% of websites need less resources to load. Javascripts take 295.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.9 kB

  • Original 42.6 kB
  • After minification 39.8 kB
  • After compression 8.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. 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 33.9 kB or 79% of the original size.

Image Optimization

-21%

Potential reduce by 25.1 kB

  • Original 120.2 kB
  • After minification 95.1 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. Obviously, Paris Voisineo needs image optimization as it can save up to 25.1 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.5 kB

  • Original 295.7 kB
  • After minification 295.1 kB
  • After compression 293.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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 1.3 kB

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.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. Paris.voisineo.com needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

80

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

paris.voisineo.com

paris.voisineo.com

349 ms

jquery-1.2.6.pack.js

jquery-1.2.6.pack.js

242 ms

global-1-1.css

global-1-1.css

165 ms

menu.js

menu.js

167 ms

fonctions.js

fonctions.js

168 ms

rating.css

rating.css

168 ms

jquery.rating.pack.js

jquery.rating.pack.js

169 ms

jquery.MetaData.js

jquery.MetaData.js

323 ms

thickbox.css

thickbox.css

325 ms

thickbox-compressed.js

thickbox-compressed.js

338 ms

page_accueil.css

page_accueil.css

165 ms

show_ads.js

show_ads.js

78 ms

v.gif

v.gif

168 ms

boutique.jpg

boutique.jpg

304 ms

h.jpg

h.jpg

158 ms

blog-sep.png

blog-sep.png

160 ms

log-valider.png

log-valider.png

161 ms

information.png

information.png

168 ms

panneau-left.gif

panneau-left.gif

172 ms

panneau-right.gif

panneau-right.gif

300 ms

menu-fond-left.png

menu-fond-left.png

323 ms

p.gif

p.gif

326 ms

m.gif

m.gif

326 ms

menu-fond-right.png

menu-fond-right.png

323 ms

fond-or2.png

fond-or2.png

338 ms

deco.gif

deco.gif

461 ms

tab_reduc.png

tab_reduc.png

479 ms

tous.gif

tous.gif

482 ms

fond-vign.png

fond-vign.png

486 ms

logo-reduc-50.png

logo-reduc-50.png

484 ms

tabtitr-vois.png

tabtitr-vois.png

495 ms

h-a.jpg

h-a.jpg

629 ms

tabtitr-rdv.png

tabtitr-rdv.png

641 ms

logo-rdv-50.png

logo-rdv-50.png

644 ms

tabtitr-annonce.png

tabtitr-annonce.png

641 ms

logo-petite-annonce2-50.png

logo-petite-annonce2-50.png

650 ms

tabtitr-groupe.png

tabtitr-groupe.png

652 ms

logo-groupe-65.png

logo-groupe-65.png

797 ms

tabtitr-ba.png

tabtitr-ba.png

799 ms

logo-commercants-50.png

logo-commercants-50.png

802 ms

not-nul.png

not-nul.png

808 ms

fond-topgri.png

fond-topgri.png

810 ms

picto-addan.png

picto-addan.png

812 ms

mini-sep.png

mini-sep.png

957 ms

picto-ami.png

picto-ami.png

960 ms

fond-footer.gif

fond-footer.gif

960 ms

fond.png

fond.png

160 ms

header-left.jpg

header-left.jpg

161 ms

header.jpg

header.jpg

267 ms

log-fond.png

log-fond.png

163 ms

log-l.png

log-l.png

170 ms

log-r.png

log-r.png

171 ms

log-fond-vign.png

log-fond-vign.png

318 ms

aide-connexion.png

aide-connexion.png

326 ms

panneau-mid.gif

panneau-mid.gif

325 ms

panneau-p1.gif

panneau-p1.gif

332 ms

panneau-p2.gif

panneau-p2.gif

335 ms

header-right.jpg

header-right.jpg

406 ms

menu-fond-2.png

menu-fond-2.png

477 ms

tab-left-on.png

tab-left-on.png

483 ms

fond-over-tab.png

fond-over-tab.png

483 ms

fond-menu-in.png

fond-menu-in.png

487 ms

tab-right-on.png

tab-right-on.png

502 ms

tab-left.png

tab-left.png

564 ms

tab-right.png

tab-right.png

641 ms

fond-midb.png

fond-midb.png

640 ms

fond-contenu.jpg

fond-contenu.jpg

649 ms

fond-blanc.gif

fond-blanc.gif

654 ms

adsbygoogle.js

adsbygoogle.js

188 ms

fond_moteur_voisins.png

fond_moteur_voisins.png

930 ms

fond-recherche.png

fond-recherche.png

636 ms

min-flech-search.gif

min-flech-search.gif

718 ms

flechesel2.png

flechesel2.png

770 ms

ok_bleu.png

ok_bleu.png

773 ms

bgBloc.png

bgBloc.png

777 ms

but_minscrire2.png

but_minscrire2.png

784 ms

fond-mid.png

fond-mid.png

794 ms

ga.js

ga.js

9 ms

__utm.gif

__utm.gif

11 ms

loadingAnimation.gif

loadingAnimation.gif

887 ms

show_ads_impl.js

show_ads_impl.js

433 ms

zrt_lookup.html

zrt_lookup.html

38 ms

ads

ads

50 ms

Accessibility Review

paris.voisineo.com accessibility score

60

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

paris.voisineo.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

paris.voisineo.com SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paris.voisineo.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Paris.voisineo.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

paris.voisineo.com

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