Tools & Wizards About Us

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

publiticket.fr

Publi Ticket | La pub au verso des tickets de caisse

Page Load Speed

3.8 sec in total

First Response

428 ms

Resources Loaded

2.6 sec

Page Rendered

818 ms

About Website

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

Créateur et leader de la publicité au dos de vos tickets de caisse, Publi Ticket est désormais une référence de la publicité locale.

Visit publiticket.fr

Key Findings

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

Performance Metrics

publiticket.fr performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

publiticket.fr

428 ms

css

48 ms

css

67 ms

css

70 ms

js

92 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 73% of them (53 requests) were addressed to the original Publiticket.fr, 12% (9 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Publiticket.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.1 kB (7%)

Content Size

4.2 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Publiticket.fr main page is 4.2 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 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 201.0 kB

  • Original 222.9 kB
  • After minification 154.0 kB
  • After compression 21.9 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 68.9 kB, which is 31% 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 201.0 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 10.0 kB

  • Original 3.5 MB
  • After minification 3.5 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. Publi Ticket images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 67 B

  • Original 443.5 kB
  • After minification 443.5 kB
  • After compression 443.4 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

-86%

Potential reduce by 88.0 kB

  • Original 102.8 kB
  • After minification 14.8 kB
  • After compression 14.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. Publiticket.fr needs all CSS files to be minified and compressed as it can save up to 88.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (21%)

Requests Now

62

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Publi Ticket. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

publiticket.fr accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

publiticket.fr best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

publiticket.fr SEO score

91

Search Engine Optimization Advices

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

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

    FR

  • Encoding

    UTF-8

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

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