Tools & Wizards About Us

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

poma.net

Bienvenue sur le site de POMA, leader du transport par câble

Page Load Speed

3.5 sec in total

First Response

171 ms

Resources Loaded

3.3 sec

Page Rendered

49 ms

About Website

Click here to check amazing POMA content for France. Otherwise, check out these important facts you probably never knew about poma.net

POMA, leader mondial du transport par câble, par les airs ou au sol. Découvrez toutes nos solutions innovantes de mobilité et leurs nombreuses applications

Visit poma.net

Key Findings

We analyzed Poma.net page load time and found that the first response time was 171 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

poma.net performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value28.4 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value3,140 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.7 s

0/100

10%

Network Requests Diagram

poma.net

171 ms

www.poma.net

433 ms

app-bf41c6888be8e0a17f79.css

161 ms

mapbox-gl.css

16 ms

formidableforms.css

317 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 97% of them (95 requests) were addressed to the original Poma.net, 2% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Api.mapbox.com. The less responsive or slowest element that took the longest time to load (619 ms) belongs to the original domain Poma.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.4 kB (62%)

Content Size

426.5 kB

After Optimization

162.0 kB

  • HTML
  • Images

In fact, the total size of Poma.net main page is 426.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 259.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 230.6 kB

  • Original 259.1 kB
  • After minification 170.5 kB
  • After compression 28.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 88.6 kB, which is 34% 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 230.6 kB or 89% of the original size.

Image Optimization

-20%

Potential reduce by 33.9 kB

  • Original 167.3 kB
  • After minification 133.5 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. Obviously, POMA needs image optimization as it can save up to 33.9 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 87 (91%)

Requests Now

96

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

poma.net accessibility score

67

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

[role] values are not valid

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

Best Practices

poma.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Missing source maps for large first-party JavaScript

SEO Factors

poma.net SEO score

80

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

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

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poma.net can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Poma.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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