Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

oosterik.com

Home page | Alles voor binnen en buiten

Page Load Speed

6.1 sec in total

First Response

424 ms

Resources Loaded

5.2 sec

Page Rendered

457 ms

oosterik.com screenshot

About Website

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

Tuincentrum Oosterik biedt u een groot assortiment tuin- en woonproducten. De mooiste tuinmeubelen, interieur en sfeerproducten vindt u in onze tuin webshop.

Visit oosterik.com

Key Findings

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

Performance Metrics

oosterik.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value23.7 s

0/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.206

60/100

15%

TTI (Time to Interactive)

Value45.3 s

0/100

10%

Network Requests Diagram

oosterik.com

424 ms

www.oosterik.com

1138 ms

style.css

381 ms

nivo-slider.css

379 ms

layerslider.css

388 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Oosterik.com, 96% (132 requests) were made to Oosterik.nl and 1% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Oosterik.nl.

Page Optimization Overview & Recommendations

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

Content Size

3.4 MB

After Optimization

2.9 MB

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

HTML Optimization

-84%

Potential reduce by 50.3 kB

  • Original 59.6 kB
  • After minification 58.8 kB
  • After compression 9.4 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.3 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 185.3 kB

  • Original 3.0 MB
  • After minification 2.8 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. Oosterik images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 142.3 kB

  • Original 226.2 kB
  • After minification 210.3 kB
  • After compression 83.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 142.3 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 112.6 kB

  • Original 135.4 kB
  • After minification 109.0 kB
  • After compression 22.8 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. Oosterik.com needs all CSS files to be minified and compressed as it can save up to 112.6 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

132

After Optimization

108

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

Accessibility Review

oosterik.com accessibility score

66

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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.

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

Best Practices

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

SEO Factors

oosterik.com SEO score

81

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

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