Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

gng.es

GnG | Revisión oficial de coche y Mantenimiento | Cambio de Neumáticos

Page Load Speed

5.3 sec in total

First Response

631 ms

Resources Loaded

4.5 sec

Page Rendered

167 ms

gng.es screenshot

About Website

Click here to check amazing GnG content for Spain. Otherwise, check out these important facts you probably never knew about gng.es

GnG es una red de talleres líder en Mecánica, Revisión y Mantenimiento de tu coche con más de 20 años de experiencia y 15 centros en Euskadi y Cantabria

Visit gng.es

Key Findings

We analyzed Gng.es page load time and found that the first response time was 631 ms and then it took 4.7 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

gng.es performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value18.8 s

0/100

10%

TBT (Total Blocking Time)

Value11,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value26.2 s

0/100

10%

Network Requests Diagram

gng.es

631 ms

reset.css

116 ms

layout_gng.css

357 ms

rollover.js

239 ms

nueva.js

240 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 93% of them (62 requests) were addressed to the original Gng.es, 3% (2 requests) were made to Staticxx.facebook.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Gng.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 429.4 kB (35%)

Content Size

1.2 MB

After Optimization

808.6 kB

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

HTML Optimization

-80%

Potential reduce by 44.0 kB

  • Original 55.0 kB
  • After minification 44.3 kB
  • After compression 11.0 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 10.6 kB, which is 19% 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 44.0 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 68.0 kB

  • Original 800.8 kB
  • After minification 732.8 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. GnG images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 140.3 kB

  • Original 181.3 kB
  • After minification 133.3 kB
  • After compression 40.9 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 140.3 kB or 77% of the original size.

CSS Optimization

-88%

Potential reduce by 177.0 kB

  • Original 201.0 kB
  • After minification 161.1 kB
  • After compression 23.9 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. Gng.es needs all CSS files to be minified and compressed as it can save up to 177.0 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

66

After Optimization

41

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

Accessibility Review

gng.es accessibility score

70

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

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

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

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

Links do not have a discernible name

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

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

gng.es best practices score

75

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

SEO Factors

gng.es SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    ES

  • Language Claimed

    ES

  • Encoding

    ISO-8859-1

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

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