Tools & Wizards About Us
emmago.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

emmago.com

Emma Go Shoes // Designed in Copenhagen // Handmade in Spain – EMMA GO SHOES

Page Load Speed

1.6 sec in total

First Response

251 ms

Resources Loaded

1.1 sec

Page Rendered

229 ms

emmago.com screenshot

About Website

Welcome to emmago.com homepage info - get ready to check Emma Go best content for France right away, or after learning these important things about emmago.com

Emma Go footwear, designed in Denmark and handmade in Spain. Emma Go is driven by a desire to make you the perfect pair of shoes! Comfort, fair wage and working condition and an honest product.

Visit emmago.com

Key Findings

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

emmago.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value3,160 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.09

92/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

emmago.com

251 ms

www.emmago.com

299 ms

fbevents.js

13 ms

timber.scss.css

46 ms

theme.scss.css

57 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Emmago.com, 45% (19 requests) were made to Cdn.shopify.com and 7% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (312 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 209.5 kB (39%)

Content Size

543.6 kB

After Optimization

334.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 28.5 kB

  • Original 35.6 kB
  • After minification 27.7 kB
  • After compression 7.0 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 7.9 kB, which is 22% 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 28.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 224.0 kB
  • After minification 224.0 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. Emma Go images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 95.2 kB

  • Original 179.9 kB
  • After minification 164.6 kB
  • After compression 84.7 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 95.2 kB or 53% of the original size.

CSS Optimization

-82%

Potential reduce by 85.8 kB

  • Original 104.2 kB
  • After minification 102.2 kB
  • After compression 18.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. Emmago.com needs all CSS files to be minified and compressed as it can save up to 85.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (80%)

Requests Now

35

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

emmago.com

emmago.com

251 ms

www.emmago.com

www.emmago.com

299 ms

fbevents.js

fbevents.js

13 ms

timber.scss.css

timber.scss.css

46 ms

theme.scss.css

theme.scss.css

57 ms

css

css

30 ms

css

css

65 ms

css

css

71 ms

ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js

ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js

35 ms

jquery.min.js

jquery.min.js

10 ms

modernizr.min.js

modernizr.min.js

51 ms

lookbooks-app.css

lookbooks-app.css

51 ms

collection-filter-v1.js

collection-filter-v1.js

69 ms

fastclick.min.js

fastclick.min.js

57 ms

timber.js

timber.js

60 ms

theme.js

theme.js

61 ms

slick.min.js

slick.min.js

62 ms

slick-theme.js

slick-theme.js

61 ms

312 ms

shopify_stats.js

shopify_stats.js

165 ms

trekkie.storefront.min.js

trekkie.storefront.min.js

187 ms

shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js

shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js

165 ms

shopify.js

shopify.js

196 ms

logo.png

logo.png

32 ms

hero_slide_1.jpg

hero_slide_1.jpg

94 ms

hero_slide_2.jpg

hero_slide_2.jpg

94 ms

ajax-loader.gif

ajax-loader.gif

30 ms

70NHEhnB-ZlzsDpQLtboKA.ttf

70NHEhnB-ZlzsDpQLtboKA.ttf

69 ms

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

84 ms

icons.woff

icons.woff

24 ms

icons.woff

icons.woff

24 ms

n6RTCDcIPWSE8UNBa4k-DLGMqOskSJahibCG-vhG9Ug.ttf

n6RTCDcIPWSE8UNBa4k-DLGMqOskSJahibCG-vhG9Ug.ttf

85 ms

identify

identify

175 ms

analytics.js

analytics.js

16 ms

record.gif

record.gif

68 ms

collect

collect

10 ms

collect

collect

91 ms

page

page

126 ms

collect

collect

9 ms

sdk.js

sdk.js

200 ms

dGVzdGluZ2NvcGVuaGFnZW4ubXlzaG9waWZ5LmNvbQ==.js

dGVzdGluZ2NvcGVuaGFnZW4ubXlzaG9waWZ5LmNvbQ==.js

101 ms

setting.js

setting.js

128 ms

Accessibility Review

emmago.com accessibility score

84

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-*] attributes do not match their roles

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

emmago.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

emmago.com SEO score

99

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Emmago.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Emmago.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

emmago.com

Open Graph data is detected on the main page of Emma Go. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: