Tools & Wizards About Us
epicland.com.mx screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

epicland.com.mx

Page Load Speed

887 ms in total

First Response

71 ms

Resources Loaded

748 ms

Page Rendered

68 ms

epicland.com.mx screenshot

About Website

Welcome to epicland.com.mx homepage info - get ready to check Epicland best content for Mexico right away, or after learning these important things about epicland.com.mx

Visit epicland.com.mx

Key Findings

We analyzed Epicland.com.mx page load time and found that the first response time was 71 ms and then it took 816 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

epicland.com.mx performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value3.8 s

83/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

password

71 ms

model

82 ms

event

162 ms

dot.txt

80 ms

jquery.min.js

53 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 35% of them (11 requests) were addressed to the original Epicland.com.mx, 13% (4 requests) were made to Static.klaviyo.com and 10% (3 requests) were made to App.facturama.mx. The less responsive or slowest element that took the longest time to load (201 ms) relates to the external source App.facturama.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.6 kB (40%)

Content Size

467.0 kB

After Optimization

282.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Epicland.com.mx main page is 467.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 233.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 156.5 kB

  • Original 195.4 kB
  • After minification 193.6 kB
  • After compression 38.9 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 156.5 kB or 80% of the original size.

JavaScript Optimization

-10%

Potential reduce by 23.5 kB

  • Original 233.6 kB
  • After minification 221.4 kB
  • After compression 210.0 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

-12%

Potential reduce by 4.6 kB

  • Original 38.0 kB
  • After minification 37.6 kB
  • After compression 33.4 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. Epicland.com.mx needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (78%)

Requests Now

27

After Optimization

6

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

password

password

71 ms

model

model

82 ms

event

event

162 ms

dot.txt

dot.txt

80 ms

jquery.min.js

jquery.min.js

53 ms

shopify-2593849457

shopify-2593849457

70 ms

vendor.min.js

vendor.min.js

45 ms

theme.js

theme.js

79 ms

sections.js

sections.js

79 ms

preloads.js

preloads.js

128 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

77 ms

theme.css

theme.css

81 ms

pretty-product-pages-script.js

pretty-product-pages-script.js

76 ms

loox.1599496878808.js

loox.1599496878808.js

67 ms

moment.min.js

moment.min.js

67 ms

moment-with-locales.min.js

moment-with-locales.min.js

126 ms

gtm.js

gtm.js

96 ms

scarab-v2.js

scarab-v2.js

127 ms

trekkie.storefront.6feac1db1e2c7d84269967dcaefdee0618af51f6.min.js

trekkie.storefront.6feac1db1e2c7d84269967dcaefdee0618af51f6.min.js

53 ms

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

52 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

50 ms

password

password

85 ms

klaviyo.js

klaviyo.js

13 ms

loadScript.js

loadScript.js

197 ms

dataClient.js

dataClient.js

201 ms

klaviyo.js

klaviyo.js

15 ms

fender_analytics.113876fdc67592e7cbfd.js

fender_analytics.113876fdc67592e7cbfd.js

17 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

18 ms

runtime.694173af1af37235b81c.js

runtime.694173af1af37235b81c.js

2 ms

sharedUtils.262b9d5b04521b0abe69.js

sharedUtils.262b9d5b04521b0abe69.js

10 ms

storeFrontStyles.css

storeFrontStyles.css

29 ms

Accessibility Review

epicland.com.mx accessibility score

89

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

Document doesn't have a <title> element

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

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

High

Page has valid source maps

SEO Factors

epicland.com.mx 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

Document doesn't have a <title> element

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

epicland.com.mx

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