Tools & Wizards About Us
fivape.org screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

fivape.org

Accueil du site - Fivape - Fédération interprofessionnelle de la vape.

Page Load Speed

4.3 sec in total

First Response

937 ms

Resources Loaded

3.2 sec

Page Rendered

149 ms

fivape.org screenshot

About Website

Visit fivape.org now to see the best up-to-date Fivape content for Czech Republic and also check out these interesting facts you probably never knew about fivape.org

Etre membre de la FIVAPE, c'est faire partie d'une organisation professionnelle engagée dans la défense des intérêts de la cigarette électronique.

Visit fivape.org

Key Findings

We analyzed Fivape.org page load time and found that the first response time was 937 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fivape.org performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

www.fivape.org

937 ms

css

39 ms

css

51 ms

reset.css

155 ms

grid.css

244 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 42% of them (32 requests) were addressed to the original Fivape.org, 17% (13 requests) were made to Maps.google.com and 13% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (937 ms) belongs to the original domain Fivape.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 709.2 kB (52%)

Content Size

1.4 MB

After Optimization

648.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fivape.org 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. Javascripts take 757.7 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 108.4 kB

  • Original 122.5 kB
  • After minification 119.1 kB
  • After compression 14.1 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 108.4 kB or 88% of the original size.

Image Optimization

-10%

Potential reduce by 38.9 kB

  • Original 408.7 kB
  • After minification 369.8 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. Fivape images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 503.7 kB

  • Original 757.7 kB
  • After minification 743.3 kB
  • After compression 254.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 503.7 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 58.2 kB

  • Original 69.2 kB
  • After minification 51.4 kB
  • After compression 11.0 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. Fivape.org needs all CSS files to be minified and compressed as it can save up to 58.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (46%)

Requests Now

65

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fivape.org

www.fivape.org

937 ms

css

css

39 ms

css

css

51 ms

reset.css

reset.css

155 ms

grid.css

grid.css

244 ms

style.css

style.css

258 ms

jquery.tools.min.js

jquery.tools.min.js

686 ms

jquery.sameheight.js

jquery.sameheight.js

173 ms

global.js

global.js

308 ms

easyslider.css

easyslider.css

334 ms

easySlider1.7.js

easySlider1.7.js

486 ms

home.css

home.css

413 ms

js

js

60 ms

colorbox.css

colorbox.css

418 ms

jquery.js

jquery.js

875 ms

jquery-migrate.min.js

jquery-migrate.min.js

577 ms

cforms2012.css

cforms2012.css

655 ms

cforms.js

cforms.js

759 ms

jquery.colorbox.js

jquery.colorbox.js

544 ms

calendar.css

calendar.css

326 ms

logo_cace.png

logo_cace.png

470 ms

visuel_header.jpg

visuel_header.jpg

471 ms

HCSP.png

HCSP.png

539 ms

10502094_627001357413830_6715227047285961069_n-e1452017253196.jpg

10502094_627001357413830_6715227047285961069_n-e1452017253196.jpg

399 ms

AL-flyer-troquez_paquet_cigarette-150x210-e1446825843787.jpg

AL-flyer-troquez_paquet_cigarette-150x210-e1446825843787.jpg

473 ms

EXPERTS.png

EXPERTS.png

469 ms

JECI-logo-e1445422895294.png

JECI-logo-e1445422895294.png

734 ms

icone_fleche.png

icone_fleche.png

595 ms

Logo-Facebook.png

Logo-Facebook.png

645 ms

all.js

all.js

36 ms

ombre_slider.png

ombre_slider.png

591 ms

icone_membres.png

icone_membres.png

599 ms

Y_TKV6o8WovbUd3m_X9aAA.ttf

Y_TKV6o8WovbUd3m_X9aAA.ttf

87 ms

bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf

bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf

88 ms

0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf

0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf

87 ms

FUDHvzEKSJww3kCxuiAo2A.ttf

FUDHvzEKSJww3kCxuiAo2A.ttf

87 ms

common.js

common.js

89 ms

map.js

map.js

90 ms

util.js

util.js

146 ms

marker.js

marker.js

148 ms

btn_prev.png

btn_prev.png

575 ms

btn_next.png

btn_next.png

631 ms

border1.png

border1.png

631 ms

border2.png

border2.png

642 ms

PIPMHY90P7jtyjpXuZ2cLKCWcynf_cDxXwCLxiixG1c.ttf

PIPMHY90P7jtyjpXuZ2cLKCWcynf_cDxXwCLxiixG1c.ttf

68 ms

lILlYDvubYemzYzN7GbLkInF5uFdDttMLvmWuJdhhgs.ttf

lILlYDvubYemzYzN7GbLkInF5uFdDttMLvmWuJdhhgs.ttf

66 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

248 ms

307 ms

onion.js

onion.js

19 ms

openhand_8_8.cur

openhand_8_8.cur

192 ms

xd_arbiter.php

xd_arbiter.php

189 ms

infowindow.js

infowindow.js

180 ms

xd_arbiter.php

xd_arbiter.php

254 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

247 ms

stats.js

stats.js

177 ms

controls.js

controls.js

174 ms

transparent.png

transparent.png

36 ms

spotlight-poi.png

spotlight-poi.png

51 ms

css

css

102 ms

google4.png

google4.png

52 ms

vt

vt

21 ms

vt

vt

21 ms

vt

vt

20 ms

vt

vt

25 ms

mapcnt6.png

mapcnt6.png

20 ms

sv5.png

sv5.png

29 ms

vt

vt

32 ms

tmapctrl.png

tmapctrl.png

18 ms

cb_scout5.png

cb_scout5.png

40 ms

tmapctrl4.png

tmapctrl4.png

22 ms

imgs8.png

imgs8.png

40 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

264 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

21 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

35 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

45 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

45 ms

Accessibility Review

fivape.org accessibility score

87

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

Best Practices

fivape.org best practices score

67

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

SEO Factors

fivape.org SEO score

91

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fivape.org can be misinterpreted by Google and other search engines. Our service has detected that French 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 Fivape.org 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

fivape.org

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