Tools & Wizards About Us
pnext.fr screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

pnext.fr

Site en construction

Page Load Speed

4.9 sec in total

First Response

333 ms

Resources Loaded

4.1 sec

Page Rendered

465 ms

pnext.fr screenshot

About Website

Welcome to pnext.fr homepage info - get ready to check Pnext best content right away, or after learning these important things about pnext.fr

Chef de projet Web - Digital à Lyon

Visit pnext.fr

Key Findings

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

Performance Metrics

pnext.fr performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

pnext.fr

333 ms

www.pnext.fr

534 ms

thomasveyne.fr

789 ms

wp-emoji-release.min.js

205 ms

styles.css

159 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Pnext.fr, 90% (54 requests) were made to Thomasveyne.fr and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Thomasveyne.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 704.4 kB (36%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pnext.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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 31.0 kB

  • Original 38.6 kB
  • After minification 33.8 kB
  • After compression 7.6 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 4.8 kB, which is 12% 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 31.0 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 31.8 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. Pnext images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 228.3 kB

  • Original 334.3 kB
  • After minification 276.3 kB
  • After compression 106.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 228.3 kB or 68% of the original size.

CSS Optimization

-89%

Potential reduce by 413.3 kB

  • Original 464.8 kB
  • After minification 401.0 kB
  • After compression 51.5 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. Pnext.fr needs all CSS files to be minified and compressed as it can save up to 413.3 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pnext.fr

pnext.fr

333 ms

www.pnext.fr

www.pnext.fr

534 ms

thomasveyne.fr

thomasveyne.fr

789 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

205 ms

styles.css

styles.css

159 ms

tweets.css

tweets.css

163 ms

font.css

font.css

163 ms

etlinefont.css

etlinefont.css

164 ms

font-awesome.min.css

font-awesome.min.css

268 ms

base.css

base.css

236 ms

skeleton.css

skeleton.css

242 ms

magnific-popup.css

magnific-popup.css

243 ms

flexslider.css

flexslider.css

245 ms

style.css

style.css

285 ms

header1.css

header1.css

313 ms

color.php

color.php

1642 ms

js_composer.css

js_composer.css

804 ms

jquery.js

jquery.js

562 ms

jquery-migrate.min.js

jquery-migrate.min.js

351 ms

jquery.form.min.js

jquery.form.min.js

365 ms

scripts.js

scripts.js

389 ms

comment-reply.min.js

comment-reply.min.js

434 ms

jquery-migrate-1.2.1.js

jquery-migrate-1.2.1.js

447 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

544 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

520 ms

jquery.smooth-scroll.js

jquery.smooth-scroll.js

530 ms

jquery.quicksand.js

jquery.quicksand.js

605 ms

modernizr.custom.js

modernizr.custom.js

612 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

740 ms

Placeholders.min.js

Placeholders.min.js

641 ms

script.js

script.js

689 ms

js_composer_front.js

js_composer_front.js

776 ms

style.css

style.css

455 ms

css

css

27 ms

lyon3.jpg

lyon3.jpg

505 ms

moi1.png

moi1.png

231 ms

starL.png

starL.png

233 ms

star.png

star.png

231 ms

IT-2yoo4w49g3c9gvfrg6gdts.jpg

IT-2yoo4w49g3c9gvfrg6gdts.jpg

351 ms

si-e1426116132668-2yoo8qbz1xnei8ir51tn9c.jpg

si-e1426116132668-2yoo8qbz1xnei8ir51tn9c.jpg

400 ms

pn-2yoo91e13ojz2i7h1a3chs.jpg

pn-2yoo91e13ojz2i7h1a3chs.jpg

422 ms

cbv38-2yoo9ata7mj3i56ux8yiv4.jpg

cbv38-2yoo9ata7mj3i56ux8yiv4.jpg

431 ms

dg-2yoo9rneytybwn7ojbqdxc.jpg

dg-2yoo9rneytybwn7ojbqdxc.jpg

535 ms

client4-2yooaxv9p51loy0lydup6o.jpg

client4-2yooaxv9p51loy0lydup6o.jpg

513 ms

client5-2yooaxm80jz84uiv6nhdz4.jpg

client5-2yooaxm80jz84uiv6nhdz4.jpg

501 ms

client6-2yooaxd6bywukr14ex42rk.jpg

client6-2yooaxd6bywukr14ex42rk.jpg

582 ms

client7-2yooax8nhodnspa911xf5s.jpg

client7-2yooax8nhodnspa911xf5s.jpg

591 ms

analytics.js

analytics.js

109 ms

rcg.jpg

rcg.jpg

704 ms

ajax-loader.gif

ajax-loader.gif

366 ms

collect

collect

14 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

358 ms

yunJt0R8tCvMyj_V4xSjafesZW2xOQ-xsNqO47m55DA.woff

yunJt0R8tCvMyj_V4xSjafesZW2xOQ-xsNqO47m55DA.woff

4 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

381 ms

Roboto-BoldCondensed-webfont.woff

Roboto-BoldCondensed-webfont.woff

429 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

447 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

448 ms

OpenSans-LightItalic-webfont.woff

OpenSans-LightItalic-webfont.woff

448 ms

OpenSans-SemiboldItalic-webfont.woff

OpenSans-SemiboldItalic-webfont.woff

469 ms

et-line.woff

et-line.woff

509 ms

Accessibility Review

pnext.fr accessibility score

75

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

Image elements do not have [alt] attributes

Best Practices

pnext.fr 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

SEO Factors

pnext.fr SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

High

robots.txt is not valid

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pnext.fr 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 Pnext.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

pnext.fr

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