Access nimes.fr. Ville de Nîmes - Site officiel de la Ville de Nîmes

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

nimes.fr

286 ms

nimes.fr

807 ms

d42b6e1bdf.css

554 ms

boilerplate.css

569 ms

ui.css

840 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 91% of them (96 requests) were addressed to the original Nimes.fr, 2% (2 requests) were made to Static.widgets.apidae-tourisme.com and 2% (2 requests) were made to Matomo.nimes.fr. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Static.widgets.apidae-tourisme.com.

Content Size

3.9 MB

After Optimization

2.7 MB

In fact, the total size of Nimes.fr main page is 3.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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 120.5 kB

Original 147.6 kB
After minification 133.8 kB
After compression 27.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 120.5 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 172.2 kB

Original 2.3 MB
After minification 2.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. Nimes images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 621.4 kB

Original 1.0 MB
After minification 865.0 kB
After compression 418.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 621.4 kB or 60% of the original size.

CSS Optimization

-67%

Potential reduce by 266.5 kB

Original 397.1 kB
After minification 312.8 kB
After compression 130.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. Nimes.fr needs all CSS files to be minified and compressed as it can save up to 266.5 kB or 67% of the original size.

Requests Now

100

After Optimization

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

Accessibility Issues

These are opportunities to improve keyboard navigation in your application.

High

[accesskey] values are not unique

High

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

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

nimes.fr

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Ville de Nîmes - Site officiel de la Ville de Nîmes

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

nimes.fr

nimes.fr

d42b6e1bdf.css

boilerplate.css

ui.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

nimes.fr

nimes.fr

d42b6e1bdf.css

boilerplate.css

ui.css

typo.css

additionnel.css

tinyscrollbar.css

sous_menu.css

jqvmap.css

jquery-ui.css

editeur.css

bxslider.css

bxslider_vdn.css

overload.css

styles.css

youmax.css

tx_realty_pi1.tpl.css

lightcase.css

results.css

tx_jfmulticontent_pi1.css

jquery-ui-1.9.2.custom.css

main.css

jquery-1.8.3.min.js

jquery.vmap.js

respond.min.js

prefixfree.min.js

sous_menu.js

jquery.tinyscrollbar.js

sticky.js

jquery-ui.js

jquery.bxslider.min.js

slider_vdn.js

youmax.js

lightcase.js

solrJsResults.js

facet_daterange_controller.js

overload.js

e9e07c5ca0.js

6855.js

jquery.countTo.js

menu.js

stylesheet.css