Your Website Score is

Similar Ranking

34
INTERNET APOTHEKE - PRODUKTSUCHMASCHINE - INET-APOTHEKE.COM
inet-apotheke.com
34
SLOGANIZER -
sloganizer.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
34
OFFIZIELLE WEBSEITE – JOURNALIST, AUTOR, PREISGEKRÖNTER SCHRIFTSTELLER IN BERLIN - HOME
murat-ham.de
34
FRL MOONSTRUCK KOCHT -
frl-moonstruck-kocht.de

Latest Sites

19
LUSTIGE STORYS AUS DEM ALLTAG - MIT ALL-IN-ONE SPASS-GARANTIE
humorkult.org
4
GALERIE SAXONIA - ALTE UND NEUE KUNST, FRANK C. KEMPE, MÜNCHEN
saxonia.com
34
AUSSENWERBUNG REGIONAL - ZUGRIFF AUF ALLE WERBETRÄGER DER AUSSENWERBUNG
aussenwerbung-regional.de
26
SUPERMARKT | WERBUNG | ANGEBOTE | – DEINE WERBUNG IM SUPERMARKT | EINKAUFSWAGEN | KASSE | MARKT-RADIO |
andre-werbung.de
19
AN WERBEBAU AUS KORSCHENBROICH - AUSSENWERBEANLAGEN UND STADTMÖBEL
an-werbebau.de
19
GOOUTBECRAZY - DER FAMILIEN REISEBLOG
gooutbecrazy.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
CloudFlare
CDN

34 frl-moonstruck-kocht.de Last Updated: 7 days

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

Desktop

Mobile

Performance Desktop Score 99%
Best Practices Desktop Score 79%
SEO Desktop Score 92%
Performance Mobile Score 88%
Best Practices Mobile Score 79%
SEO Mobile Score 92%
Page Authority Authority 32%
Domain Authority Domain Authority 25%
Moz Rank 3.2/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 22 Characters
FRL MOONSTRUCK KOCHT -
Meta Description 0 Characters
NO DATA
Effective URL 30 Characters
http://frl-moonstruck-kocht.de
Excerpt Page content
frl moonstruck kocht - frl moonstruck kocht Schnellrezept Rezepte von A bis Z Rezepte nach Kategorien Gebäck Gemüsegerichte Fleisch ...
Keywords Cloud Density
rezepte22 quinoa13 gewürfelt12 posted10 more10 read10 september9 rezept8 avocado8 gemüse7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
rezepte 22
quinoa 13
gewürfelt 12
posted 10
more 10
read 10
september 9
rezept 8
avocado 8
gemüse 7
Google Preview Your look like this in google search result
FRL MOONSTRUCK KOCHT -
http://frl-moonstruck-kocht.de
frl moonstruck kocht - frl moonstruck kocht Schnellrezept Rezepte von A bis Z Rezepte nach Kategorien Gebäck Gemüsegerichte Fleisch ...
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~86.94 KB
Code Size: ~66.62 KB
Text Size: ~20.32 KB Ratio: 23.37%

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
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
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Does not use HTTPS 4 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 30 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Initial server response time was short Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it
Properly size images Potential savings of 100 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size 442 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
Eliminate render-blocking resources Potential savings of 310 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Cumulative Layout Shift 0.003
Cumulative Layout Shift measures the movement of visible elements within the viewport
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)
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
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
Avoid chaining critical requests 12 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
Avoids enormous network payloads Total size was 346 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Reduce unused CSS Potential savings of 13 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Time to Interactive 0.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Serve images in next-gen formats Potential savings of 106 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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
Largest Contentful Paint element 790 ms
This is the largest contentful element painted within the viewport

Mobile

Mobile Screenshot
Does not use HTTPS 4 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
Initial server response time was short Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 358 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 3,480 ms
This is the largest contentful element painted within the viewport
Serve images in next-gen formats Potential savings of 102 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Total Blocking Time 20 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.6 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 Potential savings of 1,370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Defer offscreen images Potential savings of 58 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoids an excessive DOM size 442 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)
Properly size images Potential savings of 34 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Time to Interactive 3.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Server Backend Latencies 30 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
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
Reduce unused CSS Potential savings of 13 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid chaining critical requests 12 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 3.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
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
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
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted

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
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
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 200 OK
Server: nginx
Date: Tue, 01 Oct 2024 19:36:27 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Cache-Enabled: True
Link: ; rel="https://api.w.org/"
X-Httpd-Modphp: 1
Host-Header: 8441280b0c35cbc1147f8ba998a563a7
X-Proxy-Cache-Info: DT:1
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records