Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

romanengo.com

Pietro Romanengo – ROMANENGO

Page Load Speed

3.6 sec in total

First Response

456 ms

Resources Loaded

2.3 sec

Page Rendered

849 ms

romanengo.com screenshot

About Website

Welcome to romanengo.com homepage info - get ready to check ROMANENGO best content right away, or after learning these important things about romanengo.com

La confetteria artigianale più antica d’Italia.

Visit romanengo.com

Key Findings

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

Performance Metrics

romanengo.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value1,430 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

romanengo.com

456 ms

global.js

84 ms

preloads.js

70 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

34 ms

storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js

41 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 77% of them (67 requests) were addressed to the original Romanengo.com, 5% (4 requests) were made to Cdnjs.cloudflare.com and 2% (2 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (471 ms) relates to the external source Swymstore-v3free-01.swymrelay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 837.7 kB (8%)

Content Size

9.9 MB

After Optimization

9.0 MB

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

HTML Optimization

-79%

Potential reduce by 130.1 kB

  • Original 164.8 kB
  • After minification 154.2 kB
  • After compression 34.8 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 130.1 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 668.5 kB

  • Original 9.3 MB
  • After minification 8.7 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. ROMANENGO images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 34.3 kB

  • Original 354.6 kB
  • After minification 354.6 kB
  • After compression 320.4 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

-12%

Potential reduce by 4.9 kB

  • Original 41.3 kB
  • After minification 41.3 kB
  • After compression 36.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. Romanengo.com needs all CSS files to be minified and compressed as it can save up to 4.9 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (81%)

Requests Now

83

After Optimization

16

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

Accessibility Review

romanengo.com accessibility score

77

Accessibility Issues

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

<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

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

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.

Best Practices

romanengo.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

romanengo.com SEO score

86

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

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Romanengo.com can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Romanengo.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 data is detected on the main page of ROMANENGO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: