metager.de

metager.de is SSL secured

Free website and domain report on metager.de

Last Updated: 1st September, 2022 Update Now
Overview

Snoop Summary for metager.de

This is a free and comprehensive report about metager.de. Metager.de is hosted in Dettingen unter Teck, Baden-Württemberg in Germany on a server with an IP address of 49.12.118.3, where the local currency is EUR and German is the local language. Metager.de is expected to earn an estimated $18 USD per day from advertising revenue. The sale of metager.de would possibly be worth $13,111 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Metager.de is very popular with an estimated 6,297 daily unique visitors. This report was last updated 1st September, 2022.

About metager.de

Site Preview: metager.de metager.de
Title: MetaGer
Description: MetaGer offers a meta search including nearly all relevant search engines with highly protected privacy. IP-address are anonymized and not stored. No cookies, tracking-pixel or any similar technology to track users. Searching is automatically encrypted b
Keywords and Tags: anonproxy, anonym, anonym suchen, bildersuche, datenschutz, deutsch, internetsuche, metager, metager.de, metasucher, popular, privacy, privatsphäre, search engines, suchen, suchmaschine, suchmaschinen
Related Terms: frep protected, protected, similar
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$13,111 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 78,390
Alexa Reach: 0.0010%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Rank By Country

Country Alexa Rank
Switzerland Flag Switzerland 18,527
Germany Flag Germany 4,230
Denmark Flag Denmark 31,765
Egypt Flag Egypt 13,436
Netherlands Flag Netherlands 2,376
Sweden Flag Sweden 13,311

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 6,297
Monthly Visitors: 191,661
Yearly Visitors: 2,298,405
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Switzerland Flag Switzerland Daily: 88
Monthly: 2,683
Yearly: 32,178
1.4%
Germany Flag Germany Daily: 3,564
Monthly: 108,480
Yearly: 1,300,897
56.6%
Denmark Flag Denmark Daily: 38
Monthly: 1,150
Yearly: 13,790
0.6%
Egypt Flag Egypt Daily: 529
Monthly: 16,100
Yearly: 193,066
8.4%
Netherlands Flag Netherlands Daily: 1,700
Monthly: 51,748
Yearly: 620,569
27%
Other Daily: 227
Monthly: 6,900
Yearly: 82,743
3.6%
Sweden Flag Sweden Daily: 151
Monthly: 4,600
Yearly: 55,162
2.4%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $18 USD
Monthly Revenue: $546 USD
Yearly Revenue: $6,550 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Switzerland Flag Switzerland Daily: $0 USD
Monthly: $2 USD
Yearly: $29 USD
0.4%
Germany Flag Germany Daily: $15 USD
Monthly: $468 USD
Yearly: $5,608 USD
85.6%
Denmark Flag Denmark Daily: $0 USD
Monthly: $0 USD
Yearly: $3 USD
<0.1%
Egypt Flag Egypt Daily: $0 USD
Monthly: $2 USD
Yearly: $25 USD
0.4%
Netherlands Flag Netherlands Daily: $2 USD
Monthly: $71 USD
Yearly: $852 USD
13%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Sweden Flag Sweden Daily: $0 USD
Monthly: $3 USD
Yearly: $34 USD
0.5%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: metager.de 10
Domain Name: metager 7
Extension (TLD): de 2

Page Speed Analysis

Average Load Time: 1.66 seconds
Load Time Comparison: Faster than 47% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 100
Accessibility 87
Best Practices 92
SEO 100
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://metager.de/
Updated: 1st September, 2022

1.53 seconds
First Contentful Paint (FCP)
80%
12%
8%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
100

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for metager.de. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.5 s
The time taken for the page to become fully interactive.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.5 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.5 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://metager.de/
http/1.1
0
236.67400004342
239
0
308
text/html
https://metager.de/
h2
237.06499999389
607.37099999096
5279
19550
200
text/html
Document
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
h2
614.14600000717
1166.8490000302
71258
70678
200
text/css
Stylesheet
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
h2
614.31000003358
1059.1260000365
7766
7188
200
text/css
Stylesheet
https://metager.de/css/utility.css?id=fef466ab6ecff1cdd2e9ad41d0e29cc5
h2
614.87400002079
1059.9090000032
1184
608
200
text/css
Stylesheet
https://metager.de/fonts/liberationsans/stylesheet.css
h2
615.08900002809
1058.7500000256
2743
2166
200
text/css
Stylesheet
https://metager.de/js/utility.js?id=d1a442e54d879b9de1840a24f59cbdb8
h2
616.00600002566
1121.5540000121
14514
13921
200
application/javascript
Script
https://metager.de/img/metager.svg
h2
1124.3310000282
1229.6550000319
3451
2869
200
image/svg+xml
Image
https://metager.de/img/key-icon.svg
h2
1168.2420000434
1280.0980000175
4101
3519
200
image/svg+xml
Image
https://metager.de/img/icon-lupe.svg
h2
1178.7699999986
1287.9870000179
2690
2108
200
image/svg+xml
Image
https://metager.de/img/plug-in.svg
h2
1178.9660000359
1290.4630000121
2971
2389
200
image/svg+xml
Image
https://metager.de/img/lock.svg
h2
1179.2220000061
1292.2290000133
2126
1544
200
image/svg+xml
Image
https://metager.de/img/heart.svg
h2
1179.4590000063
1291.8050000444
2840
2258
200
image/svg+xml
Image
https://metager.de/img/rainbow.svg
h2
1179.8880000133
1290.7630000263
2478
1896
200
image/svg+xml
Image
https://metager.de/img/leaf.svg
h2
1180.5189999868
1392.7869999898
2643
2061
200
image/svg+xml
Image
https://metager.de/img/story-plugin.svg
h2
1180.9660000145
1491.8080000207
13767
13183
200
image/svg+xml
Image
https://metager.de/img/help-icon.svg
h2
1181.3740000362
1596.0130000021
2744
2162
200
image/svg+xml
Image
https://metager.de/img/icon-more-information.svg
h2
1181.7490000394
1401.8550000037
3261
2679
200
image/svg+xml
Image
https://metager.de/img/donate-icon.svg
h2
1182.0670000161
1394.4600000395
2635
2053
200
image/svg+xml
Image
https://metager.de/img/member-icon.svg
h2
1182.3350000195
1494.0260000294
2499
1917
200
image/svg+xml
Image
https://metager.de/img/app-icon.svg
h2
1182.5280000339
1413.5940000415
4221
3639
200
image/svg+xml
Image
https://metager.de/img/icon-map.svg
h2
1182.9160000198
1293.0850000121
2086
1504
200
image/svg+xml
Image
https://metager.de/img/icon-contact.svg
h2
1183.1130000064
1319.913000043
2970
2388
200
image/svg+xml
Image
https://metager.de/img/icon-services.svg
h2
1183.3789999946
1392.4230000121
16084
15500
200
image/svg+xml
Image
https://metager.de/img/icon-outlink.svg
h2
1183.5610000417
1291.4660000242
2656
2074
200
image/svg+xml
Image
https://metager.de/img/icon-settings.svg
h2
1183.7769999984
1378.5290000378
4794
4211
200
image/svg+xml
Image
https://metager.de/img/icon-language.svg
h2
1183.9400000172
1414.1769999987
2847
2265
200
image/svg+xml
Image
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
h2
1184.1260000365
1599.366999988
71424
70844
200
text/css
Stylesheet
https://metager.de/css/themes/startpage-only-dark.css?id=d27895eef5bbb90a719503986dc86f09
h2
1184.3080000253
1394.1160000395
7758
7180
200
text/css
Stylesheet
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
611.754
15.05
1173.668
6.161
1183.69
30.537
1215.504
8.272
1311.758
5.672
1415.644
6.886
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources — Potential savings of 90 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Metager.de should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
71258
80
Properly size images
Images can slow down the page's load time. Metager.de should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Metager.de should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Metager.de should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Metager.de should consider minifying JS files.
Reduce unused CSS — Potential savings of 132 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Metager.de should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
71424
71424
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
71258
63495
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 134 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
70844
57799
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
70678
57667
https://metager.de/js/utility.js?id=d1a442e54d879b9de1840a24f59cbdb8
13921
8865
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
7188
5568
https://metager.de/css/themes/startpage-only-dark.css?id=d27895eef5bbb90a719503986dc86f09
7180
5557
https://metager.de/fonts/liberationsans/stylesheet.css
2166
1827
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 370 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://metager.de/
371.3
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Metager.de should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://metager.de/
190
https://metager.de/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Metager.de should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://metager.de/img/metager.svg
0
Avoids enormous network payloads — Total size was 260 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
71424
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
71258
https://metager.de/img/icon-services.svg
16084
https://metager.de/js/utility.js?id=d1a442e54d879b9de1840a24f59cbdb8
14514
https://metager.de/img/story-plugin.svg
13767
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
7766
https://metager.de/css/themes/startpage-only-dark.css?id=d27895eef5bbb90a719503986dc86f09
7758
https://metager.de/
5279
https://metager.de/img/icon-settings.svg
4794
https://metager.de/img/app-icon.svg
4221
Avoids an excessive DOM size — 231 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
231
Maximum DOM Depth
12
Maximum Child Elements
16
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Metager.de should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://metager.de/
92.628
2.883
1.264
Unattributable
80.692
4.47
0.171
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
95.556
Style & Layout
52.364
Parse HTML & CSS
17.309
Rendering
15.698
Script Evaluation
13.126
Script Parsing & Compilation
1.79
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 29 requests • 260 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
29
266029
Stylesheet
6
162133
Image
20
83864
Script
1
14514
Document
1
5279
Other
1
239
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00019769131424569
3.3116244199282E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of metager.de on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Serve static assets with an efficient cache policy — 27 resources found
Metager.de can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
0
71424
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
0
71258
https://metager.de/img/icon-services.svg
0
16084
https://metager.de/js/utility.js?id=d1a442e54d879b9de1840a24f59cbdb8
0
14514
https://metager.de/img/story-plugin.svg
0
13767
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
0
7766
https://metager.de/css/themes/startpage-only-dark.css?id=d27895eef5bbb90a719503986dc86f09
0
7758
https://metager.de/img/icon-settings.svg
0
4794
https://metager.de/img/app-icon.svg
0
4221
https://metager.de/img/key-icon.svg
0
4101
https://metager.de/img/metager.svg
0
3451
https://metager.de/img/icon-more-information.svg
0
3261
https://metager.de/img/plug-in.svg
0
2971
https://metager.de/img/icon-contact.svg
0
2970
https://metager.de/img/icon-language.svg
0
2847
https://metager.de/img/heart.svg
0
2840
https://metager.de/img/help-icon.svg
0
2744
https://metager.de/fonts/liberationsans/stylesheet.css
0
2743
https://metager.de/img/icon-lupe.svg
0
2690
https://metager.de/img/icon-outlink.svg
0
2656
https://metager.de/img/leaf.svg
0
2643
https://metager.de/img/donate-icon.svg
0
2635
https://metager.de/img/member-icon.svg
0
2499
https://metager.de/img/rainbow.svg
0
2478
https://metager.de/img/lock.svg
0
2126
https://metager.de/img/icon-map.svg
0
2086
https://metager.de/css/utility.css?id=fef466ab6ecff1cdd2e9ad41d0e29cc5
0
1184
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://metager.de/img/icon-map.svg
https://metager.de/img/icon-services.svg
https://metager.de/img/icon-contact.svg
https://metager.de/img/metager.svg
https://metager.de/img/metager.svg
https://metager.de/img/help-icon.svg
https://metager.de/img/icon-more-information.svg
https://metager.de/img/icon-settings.svg
https://metager.de/img/member-icon.svg
https://metager.de/img/icon-language.svg
https://metager.de/img/donate-icon.svg
https://metager.de/img/icon-lupe.svg
https://metager.de/img/icon-lupe.svg
https://metager.de/img/app-icon.svg
https://metager.de/img/key-icon.svg
https://metager.de/img/lock.svg
https://metager.de/img/plug-in.svg
87

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of metager.de. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Metager.de may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that metager.de should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
core-js
core-js-global@3.23.3
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://metager.de/
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for metager.de. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of metager.de on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
33

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of metager.de. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of metager.de on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 83
Performance 98
Accessibility 87
Best Practices 92
SEO 100
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://metager.de/
Updated: 1st September, 2022

1.05 seconds
First Contentful Paint (FCP)
90%
6%
4%

0.02 seconds
First Input Delay (FID)
96%
4%
0%

Simulate loading on mobile
98

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for metager.de. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 1.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.7 s
The time taken for the page to become fully interactive.
Speed Index — 2.7 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://metager.de/
http/1.1
0
214.45500000846
224
0
308
text/html
https://metager.de/
h2
214.7390000755
596.79500001948
5297
19588
200
text/html
Document
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
h2
607.33200004324
969.13400001358
71258
70678
200
text/css
Stylesheet
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
h2
607.55099996459
856.83000006247
7766
7188
200
text/css
Stylesheet
https://metager.de/css/utility.css?id=fef466ab6ecff1cdd2e9ad41d0e29cc5
h2
607.78099996969
1168.600999983
1184
608
200
text/css
Stylesheet
https://metager.de/fonts/liberationsans/stylesheet.css
h2
608.05300006177
716.09300002456
2743
2166
200
text/css
Stylesheet
https://metager.de/js/utility.js?id=d1a442e54d879b9de1840a24f59cbdb8
h2
608.29400003422
820.30400005169
14514
13921
200
application/javascript
Script
https://metager.de/img/metager.svg
h2
973.09300000779
1328.6070000613
3451
2869
200
image/svg+xml
Image
https://metager.de/img/key-icon.svg
h2
1169.6529999608
1330.8909999905
4101
3519
200
image/svg+xml
Image
https://metager.de/img/icon-lupe.svg
h2
1180.4240000201
1296.5839999961
2690
2108
200
image/svg+xml
Image
https://metager.de/img/plug-in.svg
h2
1180.5210000603
1296.0560000502
2971
2389
200
image/svg+xml
Image
https://metager.de/img/lock.svg
h2
1180.7160000317
1294.7619999759
2126
1544
200
image/svg+xml
Image
https://metager.de/img/heart.svg
h2
1180.8260000544
1328.142000013
2840
2258
200
image/svg+xml
Image
https://metager.de/img/rainbow.svg
h2
1180.9900000226
1330.0130000571
2478
1896
200
image/svg+xml
Image
https://metager.de/img/leaf.svg
h2
1181.1780000571
1426.0370000266
2643
2061
200
image/svg+xml
Image
https://metager.de/img/App.svg
h2
1181.2980000395
1432.4950000737
3915
3333
200
image/svg+xml
Image
https://metager.de/img/help-icon.svg
h2
1181.5339999739
1295.1520000352
2744
2162
200
image/svg+xml
Image
https://metager.de/img/icon-more-information.svg
h2
1181.6470000194
1296.7560000252
3261
2679
200
image/svg+xml
Image
https://metager.de/img/donate-icon.svg
h2
1181.7530000117
1296.4070000453
2635
2053
200
image/svg+xml
Image
https://metager.de/img/member-icon.svg
h2
1181.9580000592
1419.6790000424
2499
1917
200
image/svg+xml
Image
https://metager.de/img/app-icon.svg
h2
1182.1590000764
1418.5580000049
4221
3639
200
image/svg+xml
Image
https://metager.de/img/icon-map.svg
h2
1182.2379999794
1419.0230000531
2086
1504
200
image/svg+xml
Image
https://metager.de/img/icon-contact.svg
h2
1182.3640000075
1419.3179999711
2970
2388
200
image/svg+xml
Image
https://metager.de/img/icon-services.svg
h2
1182.5330000138
1433.2029999932
16084
15500
200
image/svg+xml
Image
https://metager.de/img/icon-outlink.svg
h2
1182.6580000343
1432.8750000568
2656
2074
200
image/svg+xml
Image
https://metager.de/img/icon-settings.svg
h2
1182.7540000668
1331.2429999933
4794
4211
200
image/svg+xml
Image
https://metager.de/img/icon-language.svg
h2
1182.872000034
1330.4139999673
2847
2265
200
image/svg+xml
Image
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
h2
1183.0060000066
1541.2340000039
71424
70844
200
text/css
Stylesheet
https://metager.de/css/themes/startpage-only-dark.css?id=d27895eef5bbb90a719503986dc86f09
h2
1183.1960000563
1419.9570000637
7758
7180
200
text/css
Stylesheet
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
601.008
14.2
822.494
7.853
903.589
7.844
971.235
6.999
1170.895
9.537
1180.456
6.09
1186.554
36.286
1224.796
6.452
1238.897
6.638
1420.092
9.38
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Metager.de should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Metager.de should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Metager.de should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Metager.de should consider minifying JS files.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 380 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://metager.de/
383.05
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Metager.de should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://metager.de/
630
https://metager.de/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Metager.de should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://metager.de/img/metager.svg
0
Avoids enormous network payloads — Total size was 250 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
71424
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
71258
https://metager.de/img/icon-services.svg
16084
https://metager.de/js/utility.js?id=d1a442e54d879b9de1840a24f59cbdb8
14514
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
7766
https://metager.de/css/themes/startpage-only-dark.css?id=d27895eef5bbb90a719503986dc86f09
7758
https://metager.de/
5297
https://metager.de/img/icon-settings.svg
4794
https://metager.de/img/app-icon.svg
4221
https://metager.de/img/key-icon.svg
4101
Avoids an excessive DOM size — 231 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
231
Maximum DOM Depth
12
Maximum Child Elements
16
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Metager.de should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://metager.de/
418.692
9.64
4.688
Unattributable
300.556
12.972
0.784
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
413.416
Style & Layout
213.708
Parse HTML & CSS
73.628
Rendering
66.684
Script Evaluation
51.052
Script Parsing & Compilation
15.276
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 29 requests • 250 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
29
256180
Stylesheet
6
162133
Image
20
74012
Script
1
14514
Document
1
5297
Other
1
224
Media
0
0
Font
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0011616948445638
0.00013824462890625
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://metager.de/
1174
73
https://metager.de/
1110
57
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of metager.de on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Eliminate render-blocking resources — Potential savings of 460 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Metager.de should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
71258
450
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
7766
150
Reduce unused CSS — Potential savings of 131 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Metager.de should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
71424
71424
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
71258
62845
Enable text compression — Potential savings of 134 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
70844
57799
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
70678
57667
https://metager.de/js/utility.js?id=d1a442e54d879b9de1840a24f59cbdb8
13921
8865
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
7188
5568
https://metager.de/css/themes/startpage-only-dark.css?id=d27895eef5bbb90a719503986dc86f09
7180
5557
https://metager.de/fonts/liberationsans/stylesheet.css
2166
1827
First Contentful Paint (3G) — 3660 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Other

Serve static assets with an efficient cache policy — 27 resources found
Metager.de can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://metager.de/css/themes/metager-dark.css?id=ce91294897d2e8a1f5204ddefc5c32b7
0
71424
https://metager.de/css/themes/metager.css?id=20a3bfd1f74667abaad47c9c41d11144
0
71258
https://metager.de/img/icon-services.svg
0
16084
https://metager.de/js/utility.js?id=d1a442e54d879b9de1840a24f59cbdb8
0
14514
https://metager.de/css/themes/startpage-only-light.css?id=9a68df8f7494b9a6050ff750eaad87f4
0
7766
https://metager.de/css/themes/startpage-only-dark.css?id=d27895eef5bbb90a719503986dc86f09
0
7758
https://metager.de/img/icon-settings.svg
0
4794
https://metager.de/img/app-icon.svg
0
4221
https://metager.de/img/key-icon.svg
0
4101
https://metager.de/img/App.svg
0
3915
https://metager.de/img/metager.svg
0
3451
https://metager.de/img/icon-more-information.svg
0
3261
https://metager.de/img/plug-in.svg
0
2971
https://metager.de/img/icon-contact.svg
0
2970
https://metager.de/img/icon-language.svg
0
2847
https://metager.de/img/heart.svg
0
2840
https://metager.de/img/help-icon.svg
0
2744
https://metager.de/fonts/liberationsans/stylesheet.css
0
2743
https://metager.de/img/icon-lupe.svg
0
2690
https://metager.de/img/icon-outlink.svg
0
2656
https://metager.de/img/leaf.svg
0
2643
https://metager.de/img/donate-icon.svg
0
2635
https://metager.de/img/member-icon.svg
0
2499
https://metager.de/img/rainbow.svg
0
2478
https://metager.de/img/lock.svg
0
2126
https://metager.de/img/icon-map.svg
0
2086
https://metager.de/css/utility.css?id=fef466ab6ecff1cdd2e9ad41d0e29cc5
0
1184
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://metager.de/img/icon-map.svg
https://metager.de/img/icon-services.svg
https://metager.de/img/icon-contact.svg
https://metager.de/img/metager.svg
https://metager.de/img/metager.svg
https://metager.de/img/help-icon.svg
https://metager.de/img/icon-more-information.svg
https://metager.de/img/icon-settings.svg
https://metager.de/img/member-icon.svg
https://metager.de/img/icon-language.svg
https://metager.de/img/donate-icon.svg
https://metager.de/img/icon-lupe.svg
https://metager.de/img/icon-lupe.svg
https://metager.de/img/app-icon.svg
https://metager.de/img/key-icon.svg
https://metager.de/img/lock.svg
https://metager.de/img/plug-in.svg
87

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of metager.de. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Metager.de may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that metager.de should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
core-js
core-js-global@3.23.3
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://metager.de/
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for metager.de. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of metager.de on mobile screens.
Document uses legible font sizes — 97.42% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
#scroll-links>a>div
2.58%
11.4898px
97.42%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
40

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of metager.de. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of metager.de on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 49.12.118.3
Continent: Europe
Country: Germany
Germany Flag
Region: Baden-Württemberg
City: Dettingen unter Teck
Longitude: 9.4458
Latitude: 48.614
Currencies: EUR
Languages: German

Web Hosting Provider

Name IP Address
Transferred to the RIPE region on 2018-06-27T02:24:04Z.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 93/100
WOT Child Safety: 91/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: metager.de
Issued By: GeoTrust TLS DV RSA Mixed SHA256 2020 CA-1
Valid From: 3rd October, 2021
Valid To: 2nd October, 2022
Subject: CN = metager.de
Hash: 29114d88
Issuer: CN = GeoTrust TLS DV RSA Mixed SHA256 2020 CA-1
O = DigiCert Inc
S = US
Version: 2
Serial Number: 13556464618254550429212591492690348788
Serial Number (Hex): 0A32E14F34A53ED94B0DB5EBB0680AF4
Valid From: 3rd October, 2024
Valid To: 2nd October, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:12:C9:88:9B:2F:C9:44:7A:7D:12:F1:DF:40:03:42:98:92:C7:24:D6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/GeoTrustTLSDVRSAMixedSHA2562020CA-1-1.crl

Full Name:
URI:http://crl4.digicert.com/GeoTrustTLSDVRSAMixedSHA2562020CA-1-1.crl

Certificate Policies: Policy: 2.23.140.1.2.1
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/GeoTrustTLSDVRSAMixedSHA2562020CA-1.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Oct 3 14:20:58.108 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:7A:D9:E6:CC:EC:25:76:F1:9F:1F:34:22:
8D:2B:34:F1:79:C9:31:C4:18:94:F2:B4:05:F8:FB:2C:
AF:51:4D:F4:02:20:1A:BD:32:19:CD:48:93:D7:6B:E8:
5C:47:AD:3D:C4:00:F7:2A:49:30:7C:D2:DB:F1:E9:12:
53:70:5A:8D:D0:FB
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 51:A3:B0:F5:FD:01:79:9C:56:6D:B8:37:78:8F:0C:A4:
7A:CC:1B:27:CB:F7:9E:88:42:9A:0D:FE:D4:8B:05:E5
Timestamp : Oct 3 14:20:58.157 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:44:AA:6C:B1:71:F6:6B:B9:94:10:F6:55:
13:FC:53:A0:C3:AD:DA:83:99:3C:B2:28:00:75:E8:65:
AE:F0:18:90:02:20:7B:57:5A:23:7D:4B:AD:15:44:93:
FF:FF:CF:66:F7:77:12:1C:BD:F8:57:4B:38:35:4F:23:
90:6A:8A:9A:0B:11
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Oct 3 14:20:58.068 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E2:7B:3C:A5:71:2B:2B:6B:1B:09:6A:
2D:C6:9A:5D:55:C4:02:B1:36:B8:00:8D:63:EB:62:24:
7C:FA:7D:E9:18:02:21:00:FF:B7:08:55:B1:A8:7B:AB:
B2:26:02:1B:7D:0C:EA:A9:57:8B:13:54:A7:EF:DD:9A:
C3:5F:00:4A:3F:17:17:E5
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:le-2.review.metager.de
DNS:metager.es
DNS:metager.org
DNS:metager3.de
DNS:www.metager.de
DNS:metager.de
Technical

DNS Lookup

A Records

Host IP Address Class TTL
metager.de. 49.12.118.3 IN 21600

NS Records

Host Nameserver Class TTL
metager.de. ns.inwx.de. IN 21600
metager.de. ns2.inwx.de. IN 21600
metager.de. ns3.inwx.eu. IN 21600

AAAA Records

IP Address Class TTL
2a01:4f8:1c0c:80f3::1 IN 21600

MX Records

Priority Host Server Class TTL
10 metager.de. mxlb.ispgateway.de. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
metager.de. ns.inwx.de. hostmaster.inwx.de. 21600

TXT Records

Host Value Class TTL
metager.de. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 1st September, 2022
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache, private
Connection: keep-alive
Content-Security-Policy: default-src 'self'; script-src 'self'; script-src-elem 'self'; script-src-attr 'self'; style-src 'self'; style-src-elem 'self'; style-src-attr 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; frame-src 'self'; frame-ancestors 'self' https://scripts.zdv.uni-mainz.de; form-action 'self' www.paypal.com
Strict-Transport-Security: max-age=15724800

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns.inwx.de
ns2.inwx.de
ns3.inwx.eu
Full Whois: % Restricted rights.
%
% Terms and Conditions of Use
%
% The above data may only be used within the scope of technical or
% administrative necessities of Internet operation or to remedy legal
% problems.
% The use for other purposes, in particular for advertising, is not permitted.
%
% The DENIC whois service on port 43 doesn't disclose any information concerning
% the domain holder, general request and abuse contact.
% This information can be obtained through use of our web-based whois service
% available at the DENIC website:
% http://www.denic.de/en/domains/whois-service/web-whois.html
%
%

Domain: metager.de
Nserver: ns2.inwx.de
Nserver: ns3.inwx.eu
Nserver: ns.inwx.de
Status: connect
Changed: 2021-04-23T13:56:02+02:00

Nameservers

Name IP Address
ns.inwx.de 192.174.68.104
ns2.inwx.de 176.97.158.104
ns3.inwx.eu 45.87.158.53
Related

Subdomains

Domain Subdomain
code

Similar Sites

Domain Valuation Snoop Score
$10 USD 1/5
$4,473,724 USD 4/5
$10,621 USD 2/5
$283 USD 1/5
$14,598 USD 3/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address