3.4 sec in total
Click here to check amazing Brevi content for Italy. Otherwise, check out these important facts you probably never knew about brevi.eu
Passeggini e carrozzine Brevi. Dal 1953 Brevi si dedica alla produzione di articoli per la prima infanzia. Entra e scopri i nostri prodotti per bambini da 0 a 3 anni.Visit brevi.eu
We analyzed Brevi.eu page load time and found that the first response time was 501 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
brevi.eu performance score
Our browser made a total of 57 requests to load all elements on the main page. We found that 95% of them (54 requests) were addressed to the original Brevi.eu, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Brevi.eu.
Page size can be reduced by 130.7 kB (11%)
In fact, the total size of Brevi.eu main page is 1.2 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. 25% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 12.9 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 12.9 kB or 74% of the original size.
Potential reduce by 22.0 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. Brevi images are well optimized though.
Potential reduce by 66.6 kB
Potential reduce by 29.3 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. Brevi.eu needs all CSS files to be minified and compressed as it can save up to 29.3 kB or 84% of the original size.
Number of requests can be reduced by 11 (20%)
brevi.eu accessibility score
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.
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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.
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
<html> element does not have a [lang] attribute
brevi.eu best practices score
Trust and Safety
Does not use HTTPS
Ensure CSP is effective against XSS attacks
Serves images with low resolution
Registers an unload listener
Browser errors were logged to the console
brevi.eu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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/).
Document uses legible font sizes
Tap targets are not sized appropriately
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brevi.eu 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Brevi.eu 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.
Open Graph description is not detected on the main page of Brevi. 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: