Access pulm.fr. Accueil

pulm.fr screenshot

30

Performance

Renders faster than
50% of other websites
80

Accessibility

Visual factors better than
that of 49% of websites
50

Best Practices

More advanced features
available than in
19% of websites
83

SEO

Google-friendlier than
46% of websites

First Response

367 ms

Resources Loaded

8 sec

Page Rendered

363 ms

pulm.fr screenshot

About Website

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

Boutique des Presses universitaires de la Méditerranée

Visit pulm.fr

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value22.9 s

0/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value47.9 s

0/100

10%

pulm.fr

367 ms

728 ms

calendar.css

103 ms

styles-m.css

304 ms

styles-l.css

318 ms

Our browser made a total of 273 requests to load all elements on the main page. We found that 98% of them (267 requests) were addressed to the original Pulm.fr, 1% (2 requests) were made to Piwik2.univ-montp3.fr and 1% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Pulm.fr.

Content Size

7.1 MB

After Optimization

6.4 MB

In fact, the total size of Pulm.fr main page is 7.1 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. Only a small number of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 107.3 kB

Original 119.8 kB
After minification 107.3 kB
After compression 12.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. 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 107.3 kB or 90% of the original size.

Image Optimization

-8%

Potential reduce by 497.7 kB

Original 6.6 MB
After minification 6.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. Pulm images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

Original 236.0 kB
After minification 236.0 kB
After compression 234.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 4.6 kB

Original 68.8 kB
After minification 68.3 kB
After compression 64.2 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. Pulm.fr has all CSS files already compressed.

Requests Now

266

After Optimization

83

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

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 Pulm.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 Pulm.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

pulm.fr

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