Tools & Wizards About Us
emka.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

emka.com

EMKA: Company

Page Load Speed

3.8 sec in total

First Response

584 ms

Resources Loaded

3.1 sec

Page Rendered

105 ms

emka.com screenshot

About Website

Click here to check amazing EMKA content for Turkey. Otherwise, check out these important facts you probably never knew about emka.com

description

Visit emka.com

Key Findings

We analyzed Emka.com page load time and found that the first response time was 584 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

emka.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.158

73/100

15%

TTI (Time to Interactive)

Value5.3 s

72/100

10%

Network Requests Diagram

www.emka.com

584 ms

style.css

213 ms

stylesheet_1104020d29.css

324 ms

undo.css

216 ms

style.css

542 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 93% of them (26 requests) were addressed to the original Emka.com, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Emka.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 258.0 kB (24%)

Content Size

1.1 MB

After Optimization

806.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 7.2 kB

  • Original 10.5 kB
  • After minification 10.0 kB
  • After compression 3.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 7.2 kB or 69% of the original size.

Image Optimization

-4%

Potential reduce by 33.6 kB

  • Original 750.2 kB
  • After minification 716.7 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. EMKA images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 98.5 kB

  • Original 164.2 kB
  • After minification 159.2 kB
  • After compression 65.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 98.5 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 118.8 kB

  • Original 139.7 kB
  • After minification 99.0 kB
  • After compression 20.9 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. Emka.com needs all CSS files to be minified and compressed as it can save up to 118.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (67%)

Requests Now

27

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.emka.com

www.emka.com

584 ms

style.css

style.css

213 ms

stylesheet_1104020d29.css

stylesheet_1104020d29.css

324 ms

undo.css

undo.css

216 ms

style.css

style.css

542 ms

dropdown.css

dropdown.css

218 ms

default.ultimate.css

default.ultimate.css

218 ms

slidedeck.css

slidedeck.css

426 ms

search.css

search.css

427 ms

tx_ritemkaexhibitionmanager.css

tx_ritemkaexhibitionmanager.css

432 ms

emka-catalog.css

emka-catalog.css

433 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

859 ms

jquery.cycle.all-3.0.3.min.js

jquery.cycle.all-3.0.3.min.js

741 ms

jquery.easing-1.3.js

jquery.easing-1.3.js

639 ms

script.js

script.js

646 ms

slightbox.css

slightbox.css

646 ms

slimbox.2.0.4.yui.js

slimbox.2.0.4.yui.js

751 ms

jquery.socialshareprivacy.min.js

jquery.socialshareprivacy.min.js

850 ms

default.css

default.css

651 ms

ga.js

ga.js

24 ms

flag_de.gif

flag_de.gif

214 ms

pipe.gif

pipe.gif

214 ms

emka.gif

emka.gif

216 ms

EMKA-Iberica_banner_globalsite_en.png

EMKA-Iberica_banner_globalsite_en.png

1079 ms

worldmap_en_02.png

worldmap_en_02.png

758 ms

global_start_product_areas_v0.png

global_start_product_areas_v0.png

553 ms

__utm.gif

__utm.gif

23 ms

print.css

print.css

217 ms

Accessibility Review

emka.com accessibility score

74

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Links do not have a discernible name

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.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

emka.com best practices score

92

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

SEO Factors

emka.com SEO score

84

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

emka.com

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