Your Website Score is

refstore.de

Similar Ranking

9
POLOLOGO.DE - NEWS MAL ANDERS... - NACHRICHTEN, UNTERHALTUNG UND MEHR...
polologo.de
9
THE PAGE IS TEMPORARILY UNAVAILABLE
immobilienguru.de
9
THE PAGE IS TEMPORARILY UNAVAILABLE
cobol-workshop.de
9
THE PAGE IS TEMPORARILY UNAVAILABLE
baumann-ideen.de
9
GARTENBAU-ADAMOVSKY
gartenbau-adamovsky.de
8
THE PAGE IS TEMPORARILY UNAVAILABLE
blog.softwing.de
8
THE PAGE IS TEMPORARILY UNAVAILABLE
uprootcleanerpro.com

Latest Sites

26
HERZLICH WILLKOMMEN AUF RECASTGAMING.DE
recastgaming.de
93
BIEDERMEIERGITARRE - GITARRENMUSIK IM FRÜHEN 19. JAHRHUNDERT
biedermeiergitarre.jimdofree.com
31
GESCHICHTE ABITURVORBEREITUNG 2023 - GESCHICHTE KOMPAKT
geschichte-abitur.de
58
MARKETBUSINESSTIMES - AN INITIATIVE TOWARDS THE MODERN WORLD
marketbusinesstimes.com
14
HOME - MALEREIBETRIEB OLEJNIK
malereibetrieb.eu
22
HOME-OFFICE EINRICHTEN - INSPIRATION, TIPPS, WISSENSWERTES
homeoffice-einrichten.de
4
REISESUCHMASCHINE – VOM FLUG BIS ZUR PAUSCHALREISE
reisesuchmaschine.net

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

9 immobilienguru.de Last Updated: 1 week

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 82%
SEO Desktop Score 100%
Performance Mobile Score 64%
Best Practices Mobile Score 83%
SEO Mobile Score 100%
Page Authority Authority 27%
Domain Authority Domain Authority 10%
Moz Rank 2.7/10
Bounce Rate Rate 0%
Title Tag 35 Characters
THE PAGE IS TEMPORARILY UNAVAILABLE
Meta Description 0 Characters
NO DATA
Effective URL 24 Characters
http://immobilienguru.de
Excerpt Page content
The page is temporarily unavailable The page you are looking for is temporarily unavailable. Please try again later. 624c46034a5acb7827709d5d2526b760 964e4bc4e8e460d87157b1a51419cb00 ba02ef0b30ddfe25288e9623e6c77c06
Keywords Cloud Density
page1 looking1 temporarily1 unavailable1 please1 again1 later1 624c46034a5acb7827709d5d2526b7...1 964e4bc4e8e460d87157b1a51419cb...1 ba02ef0b30ddfe25288e9623e6c77c...1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
page 1
looking 1
temporarily 1
unavailable 1
please 1
again 1
later 1
624c46034a5acb782770... 1
964e4bc4e8e460d87157... 1
ba02ef0b30ddfe25288e... 1
Google Preview Your look like this in google search result
THE PAGE IS TEMPORARILY UNAVAILABLE
http://immobilienguru.de
The page is temporarily unavailable The page you are looking for is temporarily unavailable. Please try again later. 624c46034a5acb7827709d5d2526b760 964e4bc4e8e460d87157b1a51419cb00 ba02ef0b30ddfe25288e9623e6c77c06
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~489 B
Code Size: ~200 B
Text Size: ~289 B Ratio: 59.10%

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

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Use efficient cache lifetimes Est savings of 3,744 KiB
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid enormous network payloads Total size was 4,033 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Properly size images Est savings of 1,970 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimize third-party usage Third-party code blocked the main thread for 40 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
Improve image delivery Est savings of 2,360 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minify JavaScript Est savings of 4 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve images in next-gen formats Est savings of 2,368 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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)
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid chaining critical requests 8 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 element 2,560 ms
This is the largest contentful element painted within the viewport
Does not use HTTPS 1 insecure request 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
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 2.6 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 32 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources Est savings of 80 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimizes main-thread work 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Enable text compression Est savings of 7 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Server Backend Latencies 50 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
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
Avoid multiple page redirects Est savings of 190 ms
Redirects introduce additional delays before the page can be loaded
Cumulative Layout Shift 0.004
Cumulative Layout Shift measures the movement of visible elements within the viewport
Efficiently encode images Est savings of 579 KiB
Optimized images load faster and consume less cellular data
Reduce unused JavaScript Est savings of 140 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Est savings of 11 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
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)

Mobile

Mobile Screenshot
Minify JavaScript Est savings of 4 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests 8 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
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy 33 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids an excessive DOM size 321 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)
Improve image delivery Est savings of 1,470 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Efficiently encode images Est savings of 579 KiB
Optimized images load faster and consume less cellular data
Largest Contentful Paint 15.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element 14,980 ms
This is the largest contentful element painted within the viewport
Properly size images Est savings of 1,035 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Serve images in next-gen formats Est savings of 2,368 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 11 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
Document uses legible font sizes 98.33% 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 970 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 8.2 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Avoid multiple page redirects Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded
Enable text compression Est savings of 7 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage Third-party code blocked the main thread for 20 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
Time to Interactive 15.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted
Does not use HTTPS 1 insecure request 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 40 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
Use efficient cache lifetimes Est savings of 3,748 KiB
A long cache lifetime can speed up repeat visits to your page
Avoid enormous network payloads Total size was 4,037 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce unused JavaScript Est savings of 140 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

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
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
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not 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/1.1 503 Service Temporarily Unavailable
Server: nginx
Date: Mon, 02 Jun 2025 20:12:15 GMT
Content-Type: text/html
Connection: keep-alive
DNS Records DNS Resource Records associated with a hostname
View DNS Records