Tools & Wizards About Us
previa.it screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

previa.it

Previa Natural Haircare

Page Load Speed

5.9 sec in total

First Response

812 ms

Resources Loaded

4.6 sec

Page Rendered

580 ms

previa.it screenshot

About Website

Welcome to previa.it homepage info - get ready to check Previa best content right away, or after learning these important things about previa.it

Natural haircare products devoid of chemical substances, certified organic and biodynamic active principles of italian origin, a bouquet of exclusive fragrances inspired by nature, eco-packaging made ...

Visit previa.it

Key Findings

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

Performance Metrics

previa.it performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value26.0 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value26.3 s

0/100

10%

Network Requests Diagram

812 ms

aos.css

38 ms

aos.css

24 ms

theme-9f52d1.css

445 ms

stub.js

23 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 84% of them (68 requests) were addressed to the original Previa.it, 5% (4 requests) were made to Unpkg.com and 4% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Previa.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (31%)

Content Size

5.8 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Previa.it main page is 5.8 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. 70% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 86.7 kB

  • Original 105.0 kB
  • After minification 81.5 kB
  • After compression 18.2 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 23.5 kB, which is 22% 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 86.7 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 310.0 kB

  • Original 3.9 MB
  • After minification 3.6 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. Previa images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 948.2 kB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 310.8 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 948.2 kB or 75% of the original size.

CSS Optimization

-76%

Potential reduce by 432.1 kB

  • Original 567.3 kB
  • After minification 565.8 kB
  • After compression 135.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. Previa.it needs all CSS files to be minified and compressed as it can save up to 432.1 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (54%)

Requests Now

68

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

812 ms

aos.css

aos.css

38 ms

aos.css

aos.css

24 ms

theme-9f52d1.css

theme-9f52d1.css

445 ms

stub.js

stub.js

23 ms

iubenda_cs.js

iubenda_cs.js

30 ms

cwoi8zrwzkttu1na2snuo5k9e1zjqhh3.js

cwoi8zrwzkttu1na2snuo5k9e1zjqhh3.js

297 ms

core.js

core.js

637 ms

theme.js

theme.js

725 ms

front.js

front.js

280 ms

cs_instagram.js

cs_instagram.js

285 ms

pm_advancedtopmenu.js

pm_advancedtopmenu.js

277 ms

signuppm.js

signuppm.js

406 ms

signuppmfacebooklogin.js

signuppmfacebooklogin.js

406 ms

ajaxdatalayer.js

ajaxdatalayer.js

407 ms

leaflet.js

leaflet.js

526 ms

leaflet-provider.js

leaflet-provider.js

572 ms

module.js

module.js

573 ms

jquery.star-rating.min.js

jquery.star-rating.min.js

570 ms

init.js

init.js

572 ms

qdp.js

qdp.js

625 ms

jquery-ui.min.js

jquery-ui.min.js

992 ms

jquery.bxslider.js

jquery.bxslider.js

648 ms

jquery.fancybox.js

jquery.fancybox.js

648 ms

printpixel.js

printpixel.js

711 ms

responsiveslides.min.js

responsiveslides.min.js

758 ms

homeslider.js

homeslider.js

759 ms

ps_searchbar.js

ps_searchbar.js

760 ms

ps_shoppingcart.js

ps_shoppingcart.js

802 ms

chosen.jquery.min.js

chosen.jquery.min.js

813 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

815 ms

jquery.actual.min.js

jquery.actual.min.js

821 ms

jquery.form.js

jquery.form.js

822 ms

as4_plugin-17.js

as4_plugin-17.js

981 ms

pm_advancedsearch.js

pm_advancedsearch.js

904 ms

custom.js

custom.js

906 ms

aos.js

aos.js

18 ms

aos.js

aos.js

20 ms

render.78cce4571e3a8dcf2344.js

render.78cce4571e3a8dcf2344.js

45 ms

fbevents.js

fbevents.js

130 ms

recorder.js

recorder.js

171 ms

search.png

search.png

513 ms

logo_man.png

logo_man.png

515 ms

previa-b2c-logo-17199117291.jpg

previa-b2c-logo-17199117291.jpg

741 ms

previa_white.png

previa_white.png

741 ms

2.jpg

2.jpg

741 ms

1.jpg

1.jpg

742 ms

search_white.png

search_white.png

744 ms

cart.png

cart.png

743 ms

cart_white.png

cart_white.png

744 ms

2101afaaf6ea36fa42427545a9949bd9051f82d1_BANNER%20ENG.png

2101afaaf6ea36fa42427545a9949bd9051f82d1_BANNER%20ENG.png

868 ms

Banner_MOBILE_en.png

Banner_MOBILE_en.png

824 ms

7d31911d70c68706881759e6c0d2f15607929281.png

7d31911d70c68706881759e6c0d2f15607929281.png

1132 ms

goccia.png

goccia.png

800 ms

53.jpg

53.jpg

738 ms

8573fc2d6a5f21123f19fe05c89454c4.woff

8573fc2d6a5f21123f19fe05c89454c4.woff

617 ms

7dd3dc7491b4a28663ba98cc86ba8276.woff

7dd3dc7491b4a28663ba98cc86ba8276.woff

703 ms

68b231adbeb9f636679baa62db640bf0.woff

68b231adbeb9f636679baa62db640bf0.woff

724 ms

af0ba93e15cb38d80d3a9f4d8.js

af0ba93e15cb38d80d3a9f4d8.js

153 ms

54eb025cd68cf413c560fb8f42fc8ccb.woff

54eb025cd68cf413c560fb8f42fc8ccb.woff

735 ms

bedec0a66ba57cf8819683721c4de52f.woff

bedec0a66ba57cf8819683721c4de52f.woff

743 ms

7fd48656d178d1585705f565a832fb64.woff

7fd48656d178d1585705f565a832fb64.woff

722 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1209 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

748 ms

49.jpg

49.jpg

816 ms

48.jpg

48.jpg

781 ms

new_home_icon_1.png

new_home_icon_1.png

694 ms

new_home_icon_2.png

new_home_icon_2.png

705 ms

new_home_icon_5.png

new_home_icon_5.png

785 ms

new_home_icon_6.png

new_home_icon_6.png

755 ms

new_home_icon_4.png

new_home_icon_4.png

805 ms

new_home_icon_3.png

new_home_icon_3.png

813 ms

pagamenti_ok.png

pagamenti_ok.png

809 ms

earth_logo.png

earth_logo.png

814 ms

facebook-2.png

facebook-2.png

743 ms

youtube.png

youtube.png

804 ms

instagram.png

instagram.png

806 ms

linkedin-logo.svg

linkedin-logo.svg

807 ms

all.js

all.js

65 ms

all.js

all.js

5 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

563 ms

Accessibility Review

previa.it accessibility score

65

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA IDs are not unique

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

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

Impact

Issue

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.

Best Practices

previa.it best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

previa.it SEO score

83

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Previa.it can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Previa.it 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

previa.it

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