Your Website Score is

Similar Ranking

34
INTERNET APOTHEKE - PRODUKTSUCHMASCHINE - INET-APOTHEKE.COM
inet-apotheke.com
34
SLOGANIZER -
sloganizer.de
34
GOLDSAMMLER -
goldsammler.eu
34
PATRICK HERTEL - FOTOGRAF
patrick-hertel.de
34
TIPPS FÜR KMU UND STARTUP - UNTERNEHMER.DE
unternehmer.de
34
EASTERNEYE | BRITISH ASIAN WEEKLY NEWSPAPER IN UK
easterneye.biz
34
MONSTERZEUG - SCHENKEN MACHT GLÜCKLICH
monsterzeug.de

Latest Sites

21
LEARN SPANISH GRAMMAR - SPANISH GRAMMAR LESSONS
spanishgrammarlessons.com
26
MESSAGE.WS – PRESSEMELDUNGEN
message.ws
1
GAMEXTAZY.COM – ONLINE BLACKJACK
gamextazy.com
23
JGP GROUP GMBH ALLE DIENSTLEISTUNGEN AUS EINER HAND
jgp-dienstleistungen.ch
19
TAXI IN TÜBINGEN UND UMGEBUNG - WWW.TAXISTA.DE
taxista.de
17
WEBSITES & WEBSHOPS NACH SCHWEIZER QUALITÄT! - SWISS-WEBSOFT.CH
juniorsmedia.com
40
SLAPPED.DE – ONLINEMAGAZIN SEIT 2000
slapped.de

Top Technologies

PHP
Programming Languages
Apache
Web Servers
WordPress
CMS
Google Font API
Font Scripts
jQuery
JavaScript Frameworks
Nginx
Web Servers
Font Awesome
Font Scripts
Yoast SEO
SEO
Google AdSense
Advertising Networks
Twitter Bootstrap
Web Frameworks

34 patrick-hertel.de Last Updated: 3 weeks

Success 70% of passed verification steps
Warning 23% of total warning
Errors 7% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 100%
Best Practices Desktop Score 79%
SEO Desktop Score 100%
Performance Mobile Score 74%
Best Practices Mobile Score 79%
SEO Mobile Score 100%
Page Authority Authority 29%
Domain Authority Domain Authority 13%
Moz Rank 2.9/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 25 Characters
PATRICK HERTEL - FOTOGRAF
Meta Description 62 Characters
verlassene Orte, Architektur, Natur- und Landschaftsfotografie
Effective URL 28 Characters
http://www.patrick-hertel.de
Excerpt Page content
Patrick Hertel - Fotograf Zum Inhalt springen Patrick Hertel PortfolioLost PlacesLandschaftenStrange Magic RoomsFotografieKontakt Search Suche Suchen … Patrick Hertel Search Suche Suchen … Suche Suchen … Men...
Keywords Cloud Density
patrick4 hertel4 suche3 portfolio3 lost3 places3 suchen 3 kontakt3 fotografie2 search2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
patrick 4
hertel 4
suche 3
portfolio 3
lost 3
places 3
suchen  3
kontakt 3
fotografie 2
search 2
Google Preview Your look like this in google search result
PATRICK HERTEL - FOTOGRAF
http://www.patrick-hertel.de
verlassene Orte, Architektur, Natur- und Landschaftsfotografie
Robots.txt File Detected
http://patrick-hertel.de/robots.txt
Sitemap.xml File Detected
http://patrick-hertel.de/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~46.07 KB
Code Size: ~40.02 KB
Text Size: ~6.05 KB Ratio: 13.13%

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Use efficient cache lifetimes Est savings of 732 KiB
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Improve image delivery Est savings of 261 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Serve images in next-gen formats Est savings of 148 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce unused JavaScript Est savings of 62 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Minimizes main-thread work 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 3 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)
Network Round Trip Times 0 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
Minimize third-party usage Third-party code blocked the main thread for 0 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Server Backend Latencies 0 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
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Does not use HTTPS 26 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Legacy JavaScript Est savings of 36 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/articles/baseline-and-polyfills) features, unless you know you must support legacy browsers
Reduce unused CSS Est savings of 61 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Est savings of 10 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
Avoids enormous network payloads Total size was 771 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 400 ms
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources Est savings of 150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint 0.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 0.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy 17 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size 320 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)
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Initial server response time was short Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it
JavaScript execution time 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Est savings of 114 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid chaining critical requests 7 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

Mobile

Mobile Screenshot
First Contentful Paint 3.5 s
First Contentful Paint marks the time at which the first text or image is painted
Initial server response time was short Root document took 80 ms
Keep the server response time for the main document short because all other requests depend on it
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimize third-party usage Third-party code blocked the main thread for 0 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
Eliminate render-blocking resources Est savings of 1,990 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Network Round Trip Times 0 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
Serve static assets with an efficient cache policy 13 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 4,620 ms
This is the largest contentful element painted within the viewport
Avoids enormous network payloads Total size was 666 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve images in next-gen formats Est savings of 137 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid chaining critical requests 7 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
Largest Contentful Paint 4.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size 320 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)
Reduce unused CSS Est savings of 62 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index 4.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 4.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Reduce unused JavaScript Est savings of 62 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Document uses legible font sizes 100% 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Use efficient cache lifetimes Est savings of 627 KiB
A long cache lifetime can speed up repeat visits to your page
Improve image delivery Est savings of 151 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Legacy JavaScript Est savings of 36 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/articles/baseline-and-polyfills) features, unless you know you must support legacy browsers
Avoid serving legacy JavaScript to modern browsers Est savings of 10 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
Does not use HTTPS 22 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Server Backend Latencies 0 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
Minimizes main-thread work 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

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
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've 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 15 Links Relationship HTTP Status
Patrick Hertel Internal Link 200
Portfolio Internal Link 200
Lost Places Internal Link 200
Landschaften Internal Link 200
Strange Magic Rooms Internal Link 200
Fotografie Internal Link 200
Kontakt Internal Link 200
http://www.patrick-hertel.de/der-grieche/ Internal Link 200
http://www.patrick-hertel.de/checkpoint-alpha/ Internal Link 200
http://www.patrick-hertel.de/verladebunker/ Internal Link 200
http://www.patrick-hertel.de/hotel-garten-eden/ Internal Link 200
http://www.patrick-hertel.de/haus-der-anatomie/ Internal Link 200
http://www.patrick-hertel.de/ferienheim-ostalgie/ Internal Link 200
Impressum Internal Link 200
Patrick Hertel Internal Link 200

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 200 OK
Server: nginx
Date: Sun, 08 Jun 2025 17:13:27 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Link: ; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A patrick-hertel.de 5.44.111.13 IN 86298
NS patrick-hertel.de cns3.alfahosting.info IN 86400
NS patrick-hertel.de cns1.alfahosting.info IN 86400
NS patrick-hertel.de cns2.alfahosting.info IN 86400
MX patrick-hertel.de mx04.secure-mailgate.com IN 120
MX patrick-hertel.de mx03.secure-mailgate.com IN 120

About Us

Contact Info

Follow Us

Copyright 2021 - 2023 Webseitenwert.de - Alle Rechte vorbehalten | Impressum | Datenschutz | Imprint | Data Protection | Cookie-Einstellungen
Languages | English