Your Website Score is
31 herbrich.org Last Updated: 3 weeks
Success
54% of passed verification steps
Warning
23% of total warning
Errors
23% of total errors, require fast action
Share
Desktop
Mobile
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
42 Characters
HERBRICH - ACCESS THE ALTERNATE WORLD
Meta Description
144 Characters
Wir sind die Herbrich Corporation, eine Technologie unternehmen aus Hamburg und Schleswig Holstein, was als dissoziatives System angefangen hat.
Effective URL
24 Characters
https://www.herbrich.org
Excerpt
Page content
Herbrich - Access the alternate World
...
Google Preview
Your look like this in google search result
HERBRICH - ACCESS THE ALTERNATE WORLD
https://www.herbrich.org
Wir sind die Herbrich Corporation, eine Technologie unternehmen aus Hamburg und Schleswig Holstein, was als dissoziatives System angefangen hat.
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~73.36 KB
Code Size: ~39.34 KB
Text Size: ~34.02 KB Ratio: 46.37%
Social Data
Estimation Traffic and Earnings
8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly
Desktop
Avoid long main-thread tasks
5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Time to Interactive
3.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint
2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve images in next-gen formats
Est savings of 599 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Minify JavaScript
Est savings of 185 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid serving legacy JavaScript to modern browsers
Est savings of 23 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Max Potential First Input Delay
190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid large layout shifts
2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Legacy JavaScript
Est savings of 80 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Avoid enormous network payloads
Total size was 4,302 KiB
Large network payloads cost users real money and are highly correlated with long load times
JavaScript execution time
1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused CSS
Est savings of 222 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid an excessive DOM size
1,048 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Defer offscreen images
Est savings of 535 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Efficiently encode images
Est savings of 13 KiB
Optimized images load faster and consume less cellular data
Largest Contentful Paint element
2,350 ms
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy
37 resources found
A long cache lifetime can speed up repeat visits to your page
Use efficient cache lifetimes
Est savings of 523 KiB
A long cache lifetime can speed up repeat visits to your page
User Timing marks and measures
5 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Minify CSS
Est savings of 152 KiB
Minifying CSS files can reduce network payload sizes
Minimize main-thread work
2.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources
Est savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index
3.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Properly size images
Est savings of 933 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Improve image delivery
Est savings of 651 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
First Contentful Paint
1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce unused JavaScript
Est savings of 810 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests
17 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Network Round Trip Times
20 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Reduce initial server response time
Root document took 780 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time
120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Server Backend Latencies
380 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Minimize third-party usage
Third-party code blocked the main thread for 50 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Mobile
Serve images in next-gen formats
Est savings of 599 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Use efficient cache lifetimes
Est savings of 522 KiB
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint
4.0 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint
13.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Legacy JavaScript
Est savings of 80 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Reduce JavaScript execution time
1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid an excessive DOM size
922 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Network Round Trip Times
10 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Time to Interactive
22.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Server Backend Latencies
120 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Avoid large layout shifts
1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Reduce unused CSS
Est savings of 187 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Speed Index
9.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce unused JavaScript
Est savings of 808 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
Document uses legible font sizes
99.01% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Minify CSS
Est savings of 152 KiB
Minifying CSS files can reduce network payload sizes
Initial server response time was short
Root document took 560 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid serving legacy JavaScript to modern browsers
Est savings of 23 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Largest Contentful Paint element
13,760 ms
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources
Est savings of 1,160 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
User Timing marks and measures
5 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Defer offscreen images
Est savings of 780 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images
Est savings of 1,108 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Total Blocking Time
320 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid enormous network payloads
Total size was 4,240 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests
17 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Improve image delivery
Est savings of 1,184 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Minimize main-thread work
3.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code
Third-party code blocked the main thread for 310 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Serve static assets with an efficient cache policy
35 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid long main-thread tasks
15 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minify JavaScript
Est savings of 185 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Efficiently encode images
Est savings of 13 KiB
Optimized images load faster and consume less cellular data
Max Potential First Input Delay
190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links
View links
First 20 Links | Relationship | HTTP Status |
Home | Internal Link | 301 |
Herbrich Logo | Internal Link | 200 |
Home | Internal Link | 200 |
Website | Internal Link | 200 |
Wir | Internal Link | 200 |
Aleksandar Herbrich | Internal Link | 200 |
Jenni Hapunkt | Internal Link | 200 |
Michelle Quase | Internal Link | 200 |
Janine Bergmann | Internal Link | 200 |
Corporation | Internal Link | 200 |
Matrix | Internal Link | 200 |
Umbrella Corporation | Internal Link | 200 |
Allerleirauh | Internal Link | 200 |
Zentrix Network | Internal Link | 200 |
Wohngruppe Graumannsweg | Internal Link | 200 |
Dammwiesenstraße 14a | Internal Link | 200 |
Wandsbeker Chaussee 19 | Internal Link | 200 |
Wilhelmstift | Internal Link | 200 |
Diakonie Kropp | Internal Link | 200 |
Wohnheim Bethanien | Internal Link | 200 |
Alexa Rank
99,999,999
Global Rank99,999,999
-
Traffic
Search
Domain Available
Domain (TDL) and Typo | Status |
---|---|
herbrich.co | Available |
herbrich.us | Available |
herbrich.com | Already Registered |
herbrich.org | Already Registered |
herbrich.net | Already Registered |
hrbrich.org | Available |
yerbrich.org | Available |
nerbrich.org | Available |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2025 17:02:25 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Content-Encoding: gzip
Cache-Control: no-cache
Vary: Accept-Encoding,*,Accept-Encoding
Set-Cookie: JHSSID=asajnolzbrhq1joekyjho15d; domain=.herbrich.org; path=/; HttpOnly; SameSite=Lax
Set-Cookie: JHSSID=asajnolzbrhq1joekyjho15d; domain=.herbrich.org; path=/; HttpOnly; SameSite=Lax
Set-Cookie: __AntiXsrfToken=b5bb04b877b94c36b61c09bd5553f619; domain=.herbrich.org; path=/; HttpOnly
Set-Cookie: JH-JenniFrame-Client-ID=47efef5d-9a4c-4325-8468-24142180f0a5; domain=.herbrich.org; expires=Tue, 20-Jun-2056 17:02:24 GMT; path=/
X-Aspnet-Version: 4.0.30319
Cf-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=J%2BMGrTJ9cElPhr%2Fh7DrlwMYBIyKwsJc5sWYAXDILWzqGFmu3tA0ygSdAaG3WwcORFj6Isp49yHcjrb1fDxfrwt2Yr0rGCjNutKcK%2BSkFtNGxmNi90vBCdnnpUxIlVLd%2Bo%2F7j"}],"group":"cf-nel","max_age":604800}
Nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
Cf-Ray: 952cd56b2e6aac2e-YYZ
alt-svc: h3=":443"; ma=86400
server-timing: cfL4;desc="?proto=TCP&rtt=8079&min_rtt=8059&rtt_var=2306&sent=5&recv=6&lost=0&retrans=0&sent_bytes=2808&recv_bytes=465&delivery_rate=358771&cwnd=250&unsent_bytes=0&cid=c72a1b8235934eaf&ts=543&x=0"