Tools & Wizards About Us
wachswerk.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

wachswerk.com

Herstellung und Vertrieb von hochwertigen Bienenwachskerzen

Page Load Speed

8.8 sec in total

First Response

1.9 sec

Resources Loaded

6.6 sec

Page Rendered

328 ms

wachswerk.com screenshot

About Website

Click here to check amazing Wachswerk content. Otherwise, check out these important facts you probably never knew about wachswerk.com

30 Jahren hochwertige Bienenwachskerzen her. Alle unsere Kerzen bestehen aus reinem Bienenwachs, dessen Herkunft wir genau kennen.

Visit wachswerk.com

Key Findings

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

Performance Metrics

wachswerk.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.205

60/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

wachswerk.com

1861 ms

style.min.css

359 ms

front.min.css

315 ms

js_composer_front_custom.css

1086 ms

layout-styles.css

427 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 95% of them (42 requests) were addressed to the original Wachswerk.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Wachswerk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 948.0 kB (62%)

Content Size

1.5 MB

After Optimization

578.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 49.8 kB

  • Original 60.6 kB
  • After minification 59.6 kB
  • After compression 10.8 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 49.8 kB or 82% of the original size.

Image Optimization

-32%

Potential reduce by 201.1 kB

  • Original 623.9 kB
  • After minification 422.8 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. Obviously, Wachswerk needs image optimization as it can save up to 201.1 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 159.1 kB

  • Original 232.9 kB
  • After minification 230.4 kB
  • After compression 73.8 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 159.1 kB or 68% of the original size.

CSS Optimization

-88%

Potential reduce by 538.0 kB

  • Original 609.1 kB
  • After minification 555.9 kB
  • After compression 71.1 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. Wachswerk.com needs all CSS files to be minified and compressed as it can save up to 538.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (56%)

Requests Now

41

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wachswerk.com

wachswerk.com

1861 ms

style.min.css

style.min.css

359 ms

front.min.css

front.min.css

315 ms

js_composer_front_custom.css

js_composer_front_custom.css

1086 ms

layout-styles.css

layout-styles.css

427 ms

font-awesome.min.css

font-awesome.min.css

485 ms

flexslider.min.css

flexslider.min.css

605 ms

style.css

style.css

1103 ms

prettyPhoto.css

prettyPhoto.css

873 ms

style.css

style.css

540 ms

jquery.min.js

jquery.min.js

719 ms

jquery-migrate.min.js

jquery-migrate.min.js

673 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

834 ms

js.cookie.min.js

js.cookie.min.js

784 ms

woocommerce.min.js

woocommerce.min.js

858 ms

tracker.js

tracker.js

914 ms

front.min.js

front.min.js

1074 ms

css2

css2

34 ms

prettyPhoto.min.css

prettyPhoto.min.css

979 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

3151 ms

jquery.prettyPhoto.init.min.js

jquery.prettyPhoto.init.min.js

1028 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1172 ms

jquery.sticky-kit.min.js

jquery.sticky-kit.min.js

1173 ms

jquery.vendipro.js

jquery.vendipro.js

1314 ms

js_composer_front.min.js

js_composer_front.min.js

1228 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

1348 ms

hochkant_logo-2018-pngachim.png

hochkant_logo-2018-pngachim.png

227 ms

Tetraeder-Klein-400x533.jpg

Tetraeder-Klein-400x533.jpg

214 ms

Kegelgr-400x533.jpg

Kegelgr-400x533.jpg

254 ms

g014d-400x533.jpg

g014d-400x533.jpg

480 ms

Kugel2-400x533.jpg

Kugel2-400x533.jpg

475 ms

Bienenkorb-neu-400x533.jpg

Bienenkorb-neu-400x533.jpg

389 ms

Massivkegel11180-400x533.jpg

Massivkegel11180-400x533.jpg

357 ms

Massivzylinder13m60-400x533.jpg

Massivzylinder13m60-400x533.jpg

409 ms

Massivzylinder43m160-400x533.jpg

Massivzylinder43m160-400x533.jpg

490 ms

kegel-400x533.jpg

kegel-400x533.jpg

564 ms

Massivkegel2380-400x533.jpg

Massivkegel2380-400x533.jpg

590 ms

wabenkegelmittel-400x533.jpg

wabenkegelmittel-400x533.jpg

770 ms

wabenzyl-gross-400x533.jpg

wabenzyl-gross-400x533.jpg

1036 ms

312kegel-400x533.jpg

312kegel-400x533.jpg

654 ms

Wabenzylinder112-400x533.jpg

Wabenzylinder112-400x533.jpg

718 ms

723wabebzylinderl-400x533.jpg

723wabebzylinderl-400x533.jpg

784 ms

8QIJdijZitv49rDfuIg.ttf

8QIJdijZitv49rDfuIg.ttf

45 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

754 ms

Accessibility Review

wachswerk.com accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

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

wachswerk.com SEO score

90

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

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

wachswerk.com

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