Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 57

    SEO

    Google-friendlier than
    20% of websites

nocibe.com

Beauté & Cosmétiques » Parfumerie en ligne | NOCIBÉ

Page Load Speed

8.6 sec in total

First Response

1.8 sec

Resources Loaded

6.4 sec

Page Rendered

447 ms

nocibe.com screenshot

About Website

Welcome to nocibe.com homepage info - get ready to check Nocibe best content for France right away, or after learning these important things about nocibe.com

Découvrez tous les parfums, maquillages & soins ❤️ large choix de marques ✓ 2 échantillons offerts ✓ Livraison à domicile assurée! ➽ Nocibé

Visit nocibe.com

Key Findings

We analyzed Nocibe.com page load time and found that the first response time was 1.8 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

nocibe.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value4,350 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

www.nocibe.fr

1795 ms

screen.css

801 ms

94a58b62d73d44237886dbf03131f193.js

20 ms

geolocAndWeather.php

179 ms

bg.png

102 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nocibe.com, 2% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Nocibe.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (35%)

Content Size

3.3 MB

After Optimization

2.2 MB

In fact, the total size of Nocibe.com main page is 3.3 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.1 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 196.0 kB

  • Original 220.6 kB
  • After minification 207.3 kB
  • After compression 24.5 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 196.0 kB or 89% of the original size.

Image Optimization

-11%

Potential reduce by 225.9 kB

  • Original 2.1 MB
  • After minification 1.9 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. Obviously, Nocibe needs image optimization as it can save up to 225.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 482.0 kB

  • Original 690.3 kB
  • After minification 675.1 kB
  • After compression 208.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 482.0 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 237.9 kB

  • Original 286.3 kB
  • After minification 285.5 kB
  • After compression 48.4 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. Nocibe.com needs all CSS files to be minified and compressed as it can save up to 237.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (22%)

Requests Now

115

After Optimization

90

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

Accessibility Review

nocibe.com accessibility score

64

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-hidden="true"] elements contain focusable descendents

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

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

nocibe.com best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

nocibe.com SEO score

57

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

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 Nocibe.com 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 Nocibe.com 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 description is not detected on the main page of Nocibe. 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: