Your Website Score is

Similar Ranking

26
DETLEF FUNDER ART
parallelworld.eu
26
HANDARBEITSGESCHÄFT | SIMPLY STITCH-WOLLE, STOFFE, KURZWAREN
simplystitch.de
26
MESSAGE.WS – PRESSEMELDUNGEN
message.ws
26
HERZLICH WILLKOMMEN AUF RECASTGAMING.DE
recastgaming.de
26
OHLSDORF.INFO – FRIEDHOF OHLSDORF INFORMATIONSSEITE – HAMBURG
ohlsdorf.info
26
MÖBEL GRAF - IHR EINRICHTUNGSHAUS ✅ | MÖBEL GRAF
moebel-graf.de
26
WYTERY
wytery.de

Latest Sites

46
SWIPER DEMO
wysiwygwebbuilder.de
24
BLUMEN ONLINE KAUFEN UND VERSCHICKEN: BEZAHLBARE BLUMEN
bezahlbare-blumen.de
29
BLUMEN KAUFEN UND VERSCHICKEN - BLUMEN-ONLINESHOP BLUMIGO
blumigo.de
14
ONLINE-STAR-NEWS - OSN HOME
online-star-news.com
91
JUST A MOMENT...
canva.com
29
❶ SEO ANALYSIS TOOL • FREE WEBSITE TOOLS • RANK BOOSTER[NEW!]????
stiripesurse.directorylib.com
29
❶ SEO ANALYSIS TOOL • FREE WEBSITE TOOLS • RANK BOOSTER[NEW!]????
directorylib.com

Top Technologies

Apache
Web Servers
WordPress
CMS
Google Font API
Font Scripts
Nginx
Web Servers
Font Awesome
Font Scripts
Yoast SEO
SEO
Google AdSense
Advertising Networks
Twitter Bootstrap
Web Frameworks

26 ohlsdorf.info Last Updated: 2 weeks

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

Desktop

Mobile

Performance Desktop Score 79%
Best Practices Desktop Score 96%
SEO Desktop Score 83%
Performance Mobile Score 72%
Best Practices Mobile Score 96%
SEO Mobile Score 83%
Page Authority Authority 15%
Domain Authority Domain Authority 1%
Moz Rank 1.5/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 61 Characters
OHLSDORF.INFO – FRIEDHOF OHLSDORF INFORMATIONSSEITE – HAMBURG
Meta Description 0 Characters
NO DATA
Effective URL 21 Characters
https://ohlsdorf.info
Excerpt Page content
Ohlsdorf.info – Friedhof Ohlsdorf Informationsseite – Hamburg Zum Inhalt springen Menü Menü Startseit...
Keywords Cloud Density
ohlsdorf25 friedhof19 info14 hamburg13 cordes11 weiterlesen10 wilhelm7 andreas7 franz7 meyer7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
ohlsdorf 25
friedhof 19
info 14
hamburg 13
cordes 11
weiterlesen 10
wilhelm 7
andreas 7
franz 7
meyer 7
Google Preview Your look like this in google search result
OHLSDORF.INFO – FRIEDHOF OHLSDORF INFORMATIONSSEITE – HAMBUR
https://ohlsdorf.info
Ohlsdorf.info – Friedhof Ohlsdorf Informationsseite – Hamburg Zum Inhalt springen Menü Menü Startseit...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~98.6 KB
Code Size: ~64.23 KB
Text Size: ~34.37 KB Ratio: 34.86%

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
Reduce unused JavaScript Est savings of 44 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests 14 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
Reduce unused CSS Est savings of 37 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Properly size images Est savings of 1,494 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids an excessive DOM size 573 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)
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
Max Potential First Input Delay 40 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 380 ms
Keep the server response time for the main document short because all other requests depend on it
Time to Interactive 2.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoids enormous network payloads Total size was 2,417 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 668 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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
Eliminate render-blocking resources Est savings of 490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Improve image delivery Est savings of 1,673 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Largest Contentful Paint 2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Use efficient cache lifetimes Est savings of 1,387 KiB
A long cache lifetime can speed up repeat visits to your page
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Largest Contentful Paint element 2,300 ms
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy 43 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid serving legacy JavaScript to modern browsers Est savings of 0 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

Mobile

Mobile Screenshot
Server Backend Latencies 10 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
Reduce unused JavaScript Est savings of 44 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Improve image delivery Est savings of 615 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Document uses legible font sizes 98.07% 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
Eliminate render-blocking resources Est savings of 2,050 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Avoid chaining critical requests 14 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
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 6.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids enormous network payloads Total size was 1,104 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 219 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid serving legacy JavaScript to modern browsers Est savings of 0 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
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
Largest Contentful Paint element 6,460 ms
This is the largest contentful element painted within the viewport
Initial server response time was short Root document took 500 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Speed Index 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Reduce unused CSS Est savings of 37 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Serve static assets with an efficient cache policy 44 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size 573 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)
Time to Interactive 6.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Properly size images Est savings of 253 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Contentful Paint 3.0 s
First Contentful Paint marks the time at which the first text or image is painted
Use efficient cache lifetimes Est savings of 731 KiB
A long cache lifetime can speed up repeat visits to your page

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
Warning! Your title is not optimized
Description Website
Warning! Your description is not 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

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/2 200 
date: Wed, 25 Jun 2025 21:23:07 GMT
content-type: text/html; charset=UTF-8
server: cloudflare
x-ua-compatible: IE=edge
link: ; rel="https://api.w.org/"
cf-cache-status: DYNAMIC
vary: User-Agent
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=4uHwqAAQ1wqrNFpl0GzHyg4Al4eJkNLCQVZuseEZdakUYI35EVovX08dMNbR0nO60TxSTVJ9U8%2FDXkiabpmF4LQE%2FN9hsxgnGlDw5OY%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
content-encoding: gzip
cf-ray: 955786347d201b5d-WAW
alt-svc: h3=":443"; ma=86400
DNS Records DNS Resource Records associated with a hostname
View DNS Records