Tools & Wizards About Us
wetema.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

wetema.com

WeTeMa - Weser Technologie Manufaktur - Inh. Marius Heiserholt

Page Load Speed

1.9 sec in total

First Response

387 ms

Resources Loaded

1.5 sec

Page Rendered

95 ms

wetema.com screenshot

About Website

Click here to check amazing We Te Ma content. Otherwise, check out these important facts you probably never knew about wetema.com

Visit wetema.com

Key Findings

We analyzed Wetema.com page load time and found that the first response time was 387 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

wetema.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value5.8 s

66/100

10%

Network Requests Diagram

wetema.com

387 ms

widgetkit-5c14d792.css

106 ms

ribbon.css

204 ms

mootools-core.js

313 ms

core.js

204 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 87% of them (27 requests) were addressed to the original Wetema.com, 6% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (522 ms) belongs to the original domain Wetema.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.3 kB (11%)

Content Size

274.0 kB

After Optimization

244.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 13.0 kB

  • Original 17.8 kB
  • After minification 16.3 kB
  • After compression 4.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 13.0 kB or 73% of the original size.

Image Optimization

-18%

Potential reduce by 239 B

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

JavaScript Optimization

-2%

Potential reduce by 4.4 kB

  • Original 216.9 kB
  • After minification 216.9 kB
  • After compression 212.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-31%

Potential reduce by 11.7 kB

  • Original 38.0 kB
  • After minification 37.9 kB
  • After compression 26.4 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. Wetema.com needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 31% of the original size.

Requests Breakdown

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

Requests Now

25

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wetema.com

wetema.com

387 ms

widgetkit-5c14d792.css

widgetkit-5c14d792.css

106 ms

ribbon.css

ribbon.css

204 ms

mootools-core.js

mootools-core.js

313 ms

core.js

core.js

204 ms

caption.js

caption.js

205 ms

jquery.js

jquery.js

332 ms

widgetkit-c60cff49.js

widgetkit-c60cff49.js

213 ms

mootools-more.js

mootools-more.js

522 ms

mthash.js

mthash.js

306 ms

eprivacy.js

eprivacy.js

307 ms

theme.css

theme.css

434 ms

custom.css

custom.css

407 ms

uikit.js

uikit.js

411 ms

social.js

social.js

412 ms

theme.js

theme.js

419 ms

autocomplete.js

autocomplete.js

509 ms

search.js

search.js

512 ms

sticky.js

sticky.js

513 ms

lightbox.js

lightbox.js

199 ms

mediaelement-and-player.js

mediaelement-and-player.js

202 ms

spotlight.js

spotlight.js

329 ms

css

css

35 ms

logo_wetema_gross.png

logo_wetema_gross.png

104 ms

piwik.js

piwik.js

413 ms

close.png

close.png

104 ms

blank.gif

blank.gif

104 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

39 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

47 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

215 ms

ff0&text=verboten!

ff0&text=verboten!

126 ms

Accessibility Review

wetema.com accessibility score

90

Accessibility Issues

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

wetema.com SEO score

69

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

High

Page is blocked from indexing

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

    EN

  • Encoding

    UTF-8

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

wetema.com

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