Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

spiga.com.mx

Spiga Agencia Digital CDMX - Especialistas en WordPress, SEO y Shopify

Page Load Speed

3.3 sec in total

First Response

270 ms

Resources Loaded

2.8 sec

Page Rendered

307 ms

spiga.com.mx screenshot

About Website

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

Spiga Agencia digital especializada en SEO, WordPress, eCommerce, Shopify, Growth & Performance Marketing.

Visit spiga.com.mx

Key Findings

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

Performance Metrics

spiga.com.mx performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,530 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

spiga.com.mx

270 ms

spiga.mx

136 ms

style.min.css

99 ms

mediaelementplayer-legacy.min.css

103 ms

wp-mediaelement.min.css

104 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Spiga.com.mx, 28% (11 requests) were made to I0.wp.com and 10% (4 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (847 ms) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.7 kB (8%)

Content Size

1.3 MB

After Optimization

1.2 MB

In fact, the total size of Spiga.com.mx main page is 1.3 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. 55% of websites need less resources to load. Images take 750.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 92.7 kB

  • Original 123.9 kB
  • After minification 123.9 kB
  • After compression 31.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. 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 92.7 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 750.2 kB
  • After minification 750.2 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. Spiga images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.8 kB

  • Original 263.0 kB
  • After minification 263.0 kB
  • After compression 261.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 172 B

  • Original 114.1 kB
  • After minification 114.1 kB
  • After compression 113.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. Spiga.com.mx has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (49%)

Requests Now

35

After Optimization

18

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

Accessibility Review

spiga.com.mx accessibility score

98

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

[aria-hidden="true"] elements contain focusable descendents

Best Practices

spiga.com.mx best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

spiga.com.mx SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spiga.com.mx 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 Spiga.com.mx 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 Spiga. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: