Access oxatis.it. Realizzazione Siti e-Commerce | Modello SaaS

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value940 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

oxatis.it

309 ms

www.oxatis.it

416 ms

shared.css

298 ms

bootstrap-grid.css

19 ms

style.css

25 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 78% of them (92 requests) were addressed to the original Oxatis.it, 8% (10 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (679 ms) belongs to the original domain Oxatis.it.

Content Size

1.1 MB

After Optimization

876.0 kB

In fact, the total size of Oxatis.it main page is 1.1 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. 60% of websites need less resources to load. Javascripts take 452.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 56.0 kB

Original 71.5 kB
After minification 70.0 kB
After compression 15.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 56.0 kB or 78% of the original size.

Image Optimization

-18%

Potential reduce by 75.1 kB

Original 426.7 kB
After minification 351.6 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, Oxatis needs image optimization as it can save up to 75.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 48.3 kB

Original 452.5 kB
After minification 452.1 kB
After compression 404.1 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 48.3 kB or 11% of the original size.

CSS Optimization

-26%

Potential reduce by 37.1 kB

Original 141.8 kB
After minification 141.8 kB
After compression 104.7 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. Oxatis.it needs all CSS files to be minified and compressed as it can save up to 37.1 kB or 26% of the original size.

Requests Now

103

After Optimization

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

Accessibility Issues

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 interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

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

N/A
Language Claimed

IT
Encoding

ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oxatis.it can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Italian. Our system also found out that Oxatis.it 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

oxatis.it

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

Realizzazione Siti e-Commerce | Modello SaaS | MYTHO

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

oxatis.it

www.oxatis.it

shared.css

bootstrap-grid.css

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

oxatis.it

www.oxatis.it

shared.css

bootstrap-grid.css

style.css

frontAPI.min.js

oxApps.css

angularFramework.js

angular-locale_it-it.js

baseApp.js

Appscfg-L4.js

AC_RunActiveContent.js

jquery-featureList.js

style.css

style.css

prettyPhoto.js

prettyPhoto.css

coolPopups.js

priceConverter.js

pdfViewer.js

cookieManager.js

customCarrousel.js

flashCount.js

oxCheckSite.js

productBuilder.js

itemTabExtender.js

carrousel2013.js

productTabs.js

nodeParser.js

platinumProduct.js

fiche.js

app.js

gtag.min.js

HLAPI.js

windowAPI.js

WBValidationAPI.js

CPRuntime.js

current.js

OxRealTimeSearch.js

styles.min.css

site-responsive.min.css

base.min.css

css