Tools & Wizards About Us
ekooil.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ekooil.com

Suomalaista voitelua luonnosta, Eko voiteluöljy - Ekosata Oy - Etusivu

Page Load Speed

4.5 sec in total

First Response

372 ms

Resources Loaded

3.8 sec

Page Rendered

370 ms

ekooil.com screenshot

About Website

Welcome to ekooil.com homepage info - get ready to check Eko Oil best content right away, or after learning these important things about ekooil.com

Ekosata Oy valmistaa biologisesti hajoavia teräketju-, muotti- ja voiteluöljyjä, joiden voiteluominaisuudet ovat paremmat kuin mineraaliöljyjen.

Visit ekooil.com

Key Findings

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

Performance Metrics

ekooil.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.256

48/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

ekosata.fi

372 ms

ekosata.fi

606 ms

jquery.min.js

376 ms

app.css

502 ms

style.css

375 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ekooil.com, 5% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Ekosata.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.3 kB (15%)

Content Size

536.2 kB

After Optimization

457.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ekooil.com main page is 536.2 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 331.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 50.2 kB

  • Original 66.1 kB
  • After minification 63.9 kB
  • After compression 15.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 50.2 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 7.5 kB

  • Original 331.0 kB
  • After minification 323.5 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. Eko Oil images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 19.4 kB

  • Original 99.3 kB
  • After minification 99.3 kB
  • After compression 79.9 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 19.4 kB or 20% of the original size.

CSS Optimization

-3%

Potential reduce by 1.1 kB

  • Original 39.7 kB
  • After minification 39.7 kB
  • After compression 38.6 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. Ekooil.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

40

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ekosata.fi

ekosata.fi

372 ms

ekosata.fi

ekosata.fi

606 ms

jquery.min.js

jquery.min.js

376 ms

app.css

app.css

502 ms

style.css

style.css

375 ms

foundation-icons.css

foundation-icons.css

374 ms

jquery-ui-1.10.4.custom.min.css

jquery-ui-1.10.4.custom.min.css

373 ms

css

css

36 ms

cookie.css

cookie.css

370 ms

js

js

65 ms

js

js

108 ms

modernizr.js

modernizr.js

615 ms

cookieconsent-fi.js

cookieconsent-fi.js

498 ms

cookieconsent-config-fi.js

cookieconsent-config-fi.js

495 ms

script.js

script.js

494 ms

foundation.js

foundation.js

495 ms

foundation.topbar.js

foundation.topbar.js

640 ms

foundation.abide.js

foundation.abide.js

641 ms

foundation.alerts.js

foundation.alerts.js

640 ms

foundation.clearing.js

foundation.clearing.js

640 ms

foundation.cookie.js

foundation.cookie.js

639 ms

foundation.dropdown.js

foundation.dropdown.js

735 ms

foundation.forms.js

foundation.forms.js

736 ms

foundation.orbit.js

foundation.orbit.js

737 ms

foundation.reveal.js

foundation.reveal.js

739 ms

foundation.section.js

foundation.section.js

740 ms

easing.js

easing.js

739 ms

jquery.ui.totop.js

jquery.ui.totop.js

856 ms

facebook.png

facebook.png

346 ms

instagram.png

instagram.png

346 ms

ekosata.png

ekosata.png

590 ms

fin.png

fin.png

349 ms

eng.png

eng.png

348 ms

swe.png

swe.png

465 ms

568_fc35a061030fc9bf2422e9c81ad51785

568_fc35a061030fc9bf2422e9c81ad51785

1311 ms

562_fc35a061030fc9bf2422e9c81ad51785

562_fc35a061030fc9bf2422e9c81ad51785

1193 ms

538_fc35a061030fc9bf2422e9c81ad51785

538_fc35a061030fc9bf2422e9c81ad51785

1320 ms

559_fc35a061030fc9bf2422e9c81ad51785

559_fc35a061030fc9bf2422e9c81ad51785

1076 ms

458_28fd8604c13ea48e98e7451f98deab52

458_28fd8604c13ea48e98e7451f98deab52

1191 ms

500_28fd8604c13ea48e98e7451f98deab52

500_28fd8604c13ea48e98e7451f98deab52

1320 ms

460_28fd8604c13ea48e98e7451f98deab52

460_28fd8604c13ea48e98e7451f98deab52

1587 ms

501_28fd8604c13ea48e98e7451f98deab52

501_28fd8604c13ea48e98e7451f98deab52

1436 ms

467_515b5b89bf87ed4b32686541a42ed569

467_515b5b89bf87ed4b32686541a42ed569

1315 ms

542_515b5b89bf87ed4b32686541a42ed569

542_515b5b89bf87ed4b32686541a42ed569

1433 ms

491_515b5b89bf87ed4b32686541a42ed569

491_515b5b89bf87ed4b32686541a42ed569

1438 ms

ekosata-footer.png

ekosata-footer.png

1509 ms

bounce

bounce

9 ms

zepto.js

zepto.js

1323 ms

bg-top-ekosata.png

bg-top-ekosata.png

494 ms

sdk.js

sdk.js

82 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

103 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

121 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

122 ms

cookieconsent.css

cookieconsent.css

150 ms

to-top.png

to-top.png

165 ms

sdk.js

sdk.js

5 ms

Accessibility Review

ekooil.com accessibility score

87

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

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

ekooil.com best practices score

67

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

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

    FI

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

ekooil.com

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