Tools & Wizards About Us
edgestar.com.mx screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

edgestar.com.mx

EDGESTAR Accesories

Page Load Speed

1.5 sec in total

First Response

133 ms

Resources Loaded

1.1 sec

Page Rendered

258 ms

edgestar.com.mx screenshot

About Website

Click here to check amazing EDGESTAR content. Otherwise, check out these important facts you probably never knew about edgestar.com.mx

Mobile accessories in Mexico

Visit edgestar.com.mx

Key Findings

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

Performance Metrics

edgestar.com.mx performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.705

7/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

edgestar.com.mx

133 ms

boilerplate.css

47 ms

estilo.css

90 ms

foundation.css

127 ms

normalize.css

88 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 96% of them (47 requests) were addressed to the original Edgestar.com.mx, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (919 ms) belongs to the original domain Edgestar.com.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.0 kB (7%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 8.5 kB

  • Original 10.7 kB
  • After minification 9.6 kB
  • After compression 2.3 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 8.5 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 33.3 kB

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

JavaScript Optimization

-40%

Potential reduce by 50.6 kB

  • Original 127.2 kB
  • After minification 127.2 kB
  • After compression 76.6 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 50.6 kB or 40% of the original size.

CSS Optimization

-30%

Potential reduce by 6.6 kB

  • Original 21.8 kB
  • After minification 21.5 kB
  • After compression 15.2 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. Edgestar.com.mx needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (34%)

Requests Now

47

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

edgestar.com.mx

edgestar.com.mx

133 ms

boilerplate.css

boilerplate.css

47 ms

estilo.css

estilo.css

90 ms

foundation.css

foundation.css

127 ms

normalize.css

normalize.css

88 ms

css

css

24 ms

custom.modernizr.js

custom.modernizr.js

81 ms

jquery.js

jquery.js

919 ms

zepto.js

zepto.js

146 ms

foundation.js

foundation.js

118 ms

foundation.cookie.js

foundation.cookie.js

124 ms

foundation.alerts.js

foundation.alerts.js

146 ms

foundation.clearing.js

foundation.clearing.js

154 ms

foundation.forms.js

foundation.forms.js

161 ms

foundation.joyride.js

foundation.joyride.js

162 ms

foundation.magellan.js

foundation.magellan.js

159 ms

foundation.orbit.js

foundation.orbit.js

164 ms

foundation.reveal.js

foundation.reveal.js

189 ms

foundation.section.js

foundation.section.js

197 ms

index.js

index.js

196 ms

logo_edgestar.png

logo_edgestar.png

62 ms

INICIO%20ING1.jpg

INICIO%20ING1.jpg

233 ms

INICIO%20ING2.jpg

INICIO%20ING2.jpg

258 ms

INICIO%20ING3.jpg

INICIO%20ING3.jpg

207 ms

liv_hover.png

liv_hover.png

130 ms

mac_hover.png

mac_hover.png

96 ms

cpal_hover.png

cpal_hover.png

132 ms

ish_hover.png

ish_hover.png

167 ms

sea_hover.png

sea_hover.png

168 ms

1-radioshack-ne.jpg

1-radioshack-ne.jpg

205 ms

amo_hover.png

amo_hover.png

205 ms

City_Club.png

City_Club.png

244 ms

ofmx_hover.png

ofmx_hover.png

241 ms

sor_hover.png

sor_hover.png

243 ms

2-walmart-ne.jpg

2-walmart-ne.jpg

270 ms

pal_hover.png

pal_hover.png

275 ms

cel_hover.png

cel_hover.png

277 ms

com_hover.png

com_hover.png

278 ms

22-h.jpg

22-h.jpg

291 ms

5-cooppel-ne.jpg

5-cooppel-ne.jpg

305 ms

6-GoMart-ne.jpg

6-GoMart-ne.jpg

309 ms

offi_hover.png

offi_hover.png

310 ms

4-electra-ne.jpg

4-electra-ne.jpg

314 ms

6-funno-ne.jpg

6-funno-ne.jpg

325 ms

7-fibra-hotel-ne.jpg

7-fibra-hotel-ne.jpg

338 ms

8-posadas-ne.jpg

8-posadas-ne.jpg

339 ms

fb.png

fb.png

341 ms

twt.png

twt.png

337 ms

font

font

8 ms

Accessibility Review

edgestar.com.mx accessibility score

58

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

edgestar.com.mx best practices score

58

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

SEO Factors

edgestar.com.mx SEO score

82

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edgestar.com.mx can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Edgestar.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

edgestar.com.mx

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