Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 41

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

Page Load Speed

15.1 sec in total

First Response

2 sec

Resources Loaded

12.2 sec

Page Rendered

881 ms

granny.es screenshot

About Website

Welcome to granny.es homepage info - get ready to check Granny best content right away, or after learning these important things about granny.es

Nappy es la mejor tienda online para bebés de España donde podrás encontrar todo para tu bebe al mejor precio, pañales,sillas de auto,sillas de paseo, dodot..

Visit granny.es

Key Findings

We analyzed Granny.es page load time and found that the first response time was 2 sec and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

granny.es performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value34.0 s

0/100

10%

TBT (Total Blocking Time)

Value22,700 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.201

62/100

15%

TTI (Time to Interactive)

Value45.2 s

0/100

10%

Network Requests Diagram

www.nappy.es

2048 ms

brands.min.css

89 ms

css

147 ms

global.css

410 ms

product_list.css

402 ms

Our browser made a total of 193 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Granny.es, 4% (7 requests) were made to Fonts.gstatic.com and 4% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (6.8 sec) relates to the external source Nappy.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (33%)

Content Size

3.8 MB

After Optimization

2.5 MB

In fact, the total size of Granny.es main page is 3.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 550.2 kB

  • Original 593.4 kB
  • After minification 331.6 kB
  • After compression 43.2 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 261.7 kB, which is 44% 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 550.2 kB or 93% of the original size.

Image Optimization

-13%

Potential reduce by 320.6 kB

  • Original 2.5 MB
  • After minification 2.2 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. Obviously, Granny needs image optimization as it can save up to 320.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 46.9 kB

  • Original 202.0 kB
  • After minification 198.8 kB
  • After compression 155.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 46.9 kB or 23% of the original size.

CSS Optimization

-72%

Potential reduce by 325.2 kB

  • Original 451.0 kB
  • After minification 450.5 kB
  • After compression 125.8 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. Granny.es needs all CSS files to be minified and compressed as it can save up to 325.2 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 79 (43%)

Requests Now

183

After Optimization

104

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

Accessibility Review

granny.es accessibility score

41

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

granny.es best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

granny.es SEO score

85

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

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

    N/A

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Granny.es 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 Spanish. Our system also found out that Granny.es 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 description is not detected on the main page of Granny. 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: