Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

fleppy.com

Disfraces Fleppy | Tienda online Carnaval y Fiestas Temáticas

Page Load Speed

7.2 sec in total

First Response

614 ms

Resources Loaded

6.2 sec

Page Rendered

439 ms

fleppy.com screenshot

About Website

Welcome to fleppy.com homepage info - get ready to check Fleppy best content for Spain right away, or after learning these important things about fleppy.com

Tienda de disfraces de Carnaval, disfraces para Halloween y disfraces de Navidad. Cumpleaños y Fiestas.

Visit fleppy.com

Key Findings

We analyzed Fleppy.com page load time and found that the first response time was 614 ms and then it took 6.6 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

fleppy.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value700 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.734

6/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

fleppy.com

614 ms

www.fleppy.com

521 ms

330 ms

package-sf.css

420 ms

package-sf.js

705 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 89% of them (80 requests) were addressed to the original Fleppy.com, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Fleppy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 995.0 kB (37%)

Content Size

2.7 MB

After Optimization

1.7 MB

In fact, the total size of Fleppy.com main page is 2.7 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 129.7 kB

  • Original 143.9 kB
  • After minification 107.7 kB
  • After compression 14.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 36.2 kB, which is 25% 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 129.7 kB or 90% of the original size.

Image Optimization

-2%

Potential reduce by 24.8 kB

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

JavaScript Optimization

-65%

Potential reduce by 419.9 kB

  • Original 643.1 kB
  • After minification 642.2 kB
  • After compression 223.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 419.9 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 420.6 kB

  • Original 509.2 kB
  • After minification 475.5 kB
  • After compression 88.7 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. Fleppy.com needs all CSS files to be minified and compressed as it can save up to 420.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (53%)

Requests Now

86

After Optimization

40

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

Accessibility Review

fleppy.com accessibility score

81

Accessibility Issues

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

Best Practices

fleppy.com 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

High

Page has valid source maps

SEO Factors

fleppy.com SEO score

70

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

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 doesn't use 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 Fleppy.com 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 Fleppy.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 description is not detected on the main page of Fleppy. 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: