Tools & Wizards About Us
oetker.co.za screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

oetker.co.za

Frozen Pizza And Food | Dr. Oetker

Page Load Speed

2.5 sec in total

First Response

231 ms

Resources Loaded

2 sec

Page Rendered

325 ms

oetker.co.za screenshot

About Website

Visit oetker.co.za now to see the best up-to-date Oetker content and also check out these interesting facts you probably never knew about oetker.co.za

Frozen convenience meals from Dr. Oetker. We supply Frozen Pizza in many variants, frozen creamed spinach and other ready to eat frozen meals.

Visit oetker.co.za

Key Findings

We analyzed Oetker.co.za page load time and found that the first response time was 231 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

oetker.co.za performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.217

57/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

index.html

231 ms

stylesheet_8b9c2e8d89.css

85 ms

common.css

114 ms

UploadPromotion.css

172 ms

all.js

298 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 15% of them (4 requests) were addressed to the original Oetker.co.za, 46% (12 requests) were made to Az818487.vo.msecnd.net and 27% (7 requests) were made to Az809444.vo.msecnd.net. The less responsive or slowest element that took the longest time to load (996 ms) relates to the external source Az809444.vo.msecnd.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 719.9 kB (37%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Oetker.co.za main page is 1.9 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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 56.6 kB

  • Original 64.5 kB
  • After minification 53.6 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 10.9 kB, which is 17% 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 56.6 kB or 88% of the original size.

Image Optimization

-18%

Potential reduce by 245.5 kB

  • Original 1.4 MB
  • After minification 1.1 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. Obviously, Oetker needs image optimization as it can save up to 245.5 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-86%

Potential reduce by 417.8 kB

  • Original 486.7 kB
  • After minification 485.4 kB
  • After compression 69.0 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. Oetker.co.za needs all CSS files to be minified and compressed as it can save up to 417.8 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

19

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oetker. According to our analytics all requests are already optimized.

Network Requests Diagram

index.html

index.html

231 ms

stylesheet_8b9c2e8d89.css

stylesheet_8b9c2e8d89.css

85 ms

common.css

common.css

114 ms

UploadPromotion.css

UploadPromotion.css

172 ms

all.js

all.js

298 ms

startseite-borduere-280.jpg

startseite-borduere-280.jpg

416 ms

startseite-kachelbg.jpg

startseite-kachelbg.jpg

743 ms

background.jpg

background.jpg

171 ms

oetker-logo.svg

oetker-logo.svg

94 ms

back-button.svg

back-button.svg

97 ms

toc-bg.png

toc-bg.png

174 ms

388d6000-9737-4e40-aae4-30327ebbfeab.woff

388d6000-9737-4e40-aae4-30327ebbfeab.woff

173 ms

cdad12a4-819d-427e-833f-55f0c6279fb9.woff

cdad12a4-819d-427e-833f-55f0c6279fb9.woff

173 ms

488 ms

RobotoCondensed-Light-webfont.woff

RobotoCondensed-Light-webfont.woff

63 ms

RobotoCondensed-Regular-webfont.woff

RobotoCondensed-Regular-webfont.woff

129 ms

RobotoCondensed-Bold-webfont.woff

RobotoCondensed-Bold-webfont.woff

128 ms

icon-font.woff

icon-font.woff

62 ms

oetBaseDarksite

oetBaseDarksite

91 ms

1624265

1624265

996 ms

2115696

2115696

800 ms

1330691

1330691

635 ms

704091

704091

336 ms

704271

704271

593 ms

75acc85e-3b94-39fa-81c1-f5709594fdd4

75acc85e-3b94-39fa-81c1-f5709594fdd4

181 ms

267 ms

Accessibility Review

oetker.co.za accessibility score

76

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

High

Links do not have a discernible name

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.

Best Practices

oetker.co.za best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

oetker.co.za SEO score

79

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

High

Image elements do not have [alt] attributes

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

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 Oetker.co.za 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 Oetker.co.za 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

oetker.co.za

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