Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 0

    Best Practices

  • 64

    SEO

    Google-friendlier than
    24% of websites

giave.com

Giave - Maquinaria para la impresión y la conversión de materiales flexibles

Page Load Speed

5.2 sec in total

First Response

376 ms

Resources Loaded

4.6 sec

Page Rendered

166 ms

giave.com screenshot

About Website

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

En Giave somos líderes en la fabricación y suministro de maquinaria para la impresión y conversión de embalaje flexible y derivados

Visit giave.com

Key Findings

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

Performance Metrics

giave.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value3,120 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

giave.com

376 ms

1005 ms

consent.js

37 ms

style.min.css

183 ms

styles.css

272 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 88% of them (44 requests) were addressed to the original Giave.com, 4% (2 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Giave.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.0 kB (19%)

Content Size

1.2 MB

After Optimization

965.2 kB

In fact, the total size of Giave.com 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. 40% of websites need less resources to load. Images take 894.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 30.8 kB

  • Original 38.9 kB
  • After minification 37.4 kB
  • After compression 8.1 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 30.8 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 4.6 kB

  • Original 894.6 kB
  • After minification 890.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. Giave images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 107.2 kB

  • Original 157.3 kB
  • After minification 120.9 kB
  • After compression 50.0 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 107.2 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 89.3 kB

  • Original 106.4 kB
  • After minification 97.3 kB
  • After compression 17.1 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. Giave.com needs all CSS files to be minified and compressed as it can save up to 89.3 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

20

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

Accessibility Review

giave.com accessibility score

75

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

SEO Factors

giave.com SEO score

64

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

    ES

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Giave.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Giave.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 Giave. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: