Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

friking.es

Tienda de camisetas originales para toda la familia - Friking.es

Page Load Speed

7.4 sec in total

First Response

646 ms

Resources Loaded

2.4 sec

Page Rendered

4.4 sec

friking.es screenshot

About Website

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

Presentamos un amplio catálogo de camisetas originales y productos frikis al mejor precio. Tu tienda de camisetas divertidas para toda la familia

Visit friking.es

Key Findings

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

Performance Metrics

friking.es performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value4,370 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.367

29/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

www.friking.es

646 ms

gtm.js

64 ms

constants.js

37 ms

pubsub.js

92 ms

global.js

42 ms

Our browser made a total of 165 requests to load all elements on the main page. We found that 50% of them (83 requests) were addressed to the original Friking.es, 41% (68 requests) were made to Cdn.shopify.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (891 ms) relates to the external source Cdn.shopify.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 427.9 kB (6%)

Content Size

7.3 MB

After Optimization

6.9 MB

In fact, the total size of Friking.es main page is 7.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. Only a small number of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 418.3 kB

  • Original 473.0 kB
  • After minification 442.2 kB
  • After compression 54.7 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 418.3 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 795 B

  • Original 6.6 MB
  • After minification 6.6 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. Friking images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 7.8 kB

  • Original 272.3 kB
  • After minification 272.2 kB
  • After compression 264.4 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

-5%

Potential reduce by 973 B

  • Original 19.1 kB
  • After minification 19.1 kB
  • After compression 18.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. Friking.es has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (32%)

Requests Now

162

After Optimization

110

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

Accessibility Review

friking.es accessibility score

83

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

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

friking.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

friking.es SEO score

90

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

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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