Your Website Score is

Similar Ranking

51
BUFFED - DAS PORTAL FÜR ONLINE-SPIELE, FILME, SERIEN & NERD-KRAMS
buffed.de
49
WEBSITE PRÜFEN - BERICHT ÜBER DEN SEO WERT DEINER WEBSITE
website-pruefen.de
46
FAHRSERVICE TÜBINGEN STUTTGART | IMMER 15% ↗️ GÜNSTIGER
taxista.de
46
DEUTSCHE BACKLINKS KAUFEN & VERKAUFEN - TEXTLINK MARKTPLATZ
refstore.de
46
46
INSPIRIERENDE ZITATE, SPRÜCHE, SPRICHWÖRTER & APHORISMEN - WELT-DER-ZITATE.COM
welt-der-zitate.com

Latest Sites

15
FENRISSHOP - FENRISSHOP... SCHMUCK UND MEHR
fenrisshop.com
3
THE PAGE IS TEMPORARILY UNAVAILABLE
verdemed.eu
22
AX ELECTRICAL SERVICES | RELIABLE LONDON BASED ELECTRICIANS
axelectricalservices.co.uk
4
GSTART.DE KLEINANZEIGEN SUCHEN UND FINDEN
gstart.de
7
THE PAGE IS TEMPORARILY UNAVAILABLE
immobilienguru.de
23
KUMMERKASTEN CHAT - BEI KUMMER UND SORGEN OHNE ANMELDUNG
kummerkasten-chat.de
12
TANDEMPILOT.CH  +41 79 333 75 53 BRAUCHST EIN TANDEMPILOT
tandempilot.ch

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

51 buffed.de Last Updated: 4 weeks

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

Desktop

Mobile

Performance Desktop Score 89%
Best Practices Desktop Score 75%
SEO Desktop Score 91%
PWA Desktop Score 33%
Performance Mobile Score 45%
Best Practices Mobile Score 75%
SEO Mobile Score 92%
PWA Mobile Score 40%
Page Authority Authority 52%
Domain Authority Domain Authority 63%
Moz Rank 5.2/10
Bounce Rate Rate 0%
Title Tag 69 Characters
BUFFED - DAS PORTAL FÜR ONLINE-SPIELE, FILME, SERIEN & NERD-KRAMS
Meta Description 137 Characters
buffed.de - hier gibt's MMOs wie WoW, Lost Ark, Final Fantasy, Pokémon Go, Destiny 2, und Influencer, Serien, Filme, Anime und Meinungen!
Effective URL 21 Characters
https://www.buffed.de
Excerpt Page content
buffed - Das Portal für Online-Spiele, Filme, Serien & Nerd-Krams buffed.de buffed.de WoW-Datenbank Hearthstone-DB Suche Schau in die akt...
Keywords Cloud Density
dragonflight33 guide25 euch21 patch21 sich20 dungeons17 besten17 nicht15 buffed14 kolumne14
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
dragonflight 33
guide 25
euch 21
patch 21
sich 20
dungeons 17
besten 17
nicht 15
buffed 14
kolumne 14
Google Preview Your look like this in google search result
BUFFED - DAS PORTAL FÜR ONLINE-SPIELE, FILME, SERIEN & N
https://www.buffed.de
buffed.de - hier gibt's MMOs wie WoW, Lost Ark, Final Fantasy, Pokémon Go, Destiny 2, und Influencer, Serien, Filme, Anime und Meinungen!
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~351.96 KB
Code Size: ~343.6 KB
Text Size: ~8.36 KB Ratio: 2.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

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

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

Desktop

Desktop Screenshot
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
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
Minimizes main-thread work 1.3 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
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
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 1.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,430 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid an excessive DOM size 2,686 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)
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
Properly size images Potential savings of 278 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Reduce unused JavaScript Potential savings of 388 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve images in next-gen formats Potential savings of 104 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Initial server response time was short Root document took 250 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 Potential savings of 18 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Serve static assets with an efficient cache policy 125 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.04
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce unused CSS Potential savings of 201 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Keep request counts low and transfer sizes small 145 requests • 2,430 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources Potential savings of 620 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 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Includes front-end JavaScript libraries with known security vulnerabilities 18 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible

Mobile

Mobile Screenshot
Defer offscreen images Potential savings of 86 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Total Blocking Time 800 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
User Timing marks and measures 3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Largest Contentful Paint 7.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index 4.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Minimize main-thread work 2.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused JavaScript Potential savings of 283 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests 6 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 JavaScript execution time 1.6 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 90 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
Keep request counts low and transfer sizes small 61 requests • 1,024 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids an excessive DOM size 625 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 9.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint 2.4 s
First Meaningful Paint measures when the primary content of a page is visible
Max Potential First Input Delay 660 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Includes front-end JavaScript libraries with known security vulnerabilities 17 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid serving legacy JavaScript to modern browsers Potential savings of 19 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Serve images in next-gen formats Potential savings of 19 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Document uses legible font sizes 99.43% 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
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Serve static assets with an efficient cache policy 44 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Potential savings of 840 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid long main-thread tasks 11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoids enormous network payloads Total size was 1,024 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce unused CSS Potential savings of 73 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Contentful Paint 2.4 s
First Contentful Paint marks the time at which the first text or image is painted
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 1 element found
This is the largest contentful element painted within the viewport
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
Initial server response time was short Root document took 160 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint (3G) 5207 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

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
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
Congratulations! Your Domain Authority is good
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/1.1 200 OK
Date: Tue, 10 Jan 2023 16:01:25 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Set-Cookie: cfid=9e4d78b4-4255-468e-9f63-d4732b648d60;Path=/;Expires=Mon, 30-Jan-2023 17:39:29 UTC;HttpOnly
Set-Cookie: cftoken=0;Path=/;Expires=Mon, 30-Jan-2023 17:39:29 UTC;HttpOnly
Set-Cookie: CPTBP=2149035;Path=/;Domain=buffed.de
X-UA-Compatible: IE=edge
Content-Encoding: gzip
Cache-Control: max-age=0
Expires: Tue, 10 Jan 2023 16:01:25 GMT
X-Clacks-Overhead: GNU Terry Pratchett
CF-Cache-Status: DYNAMIC
Strict-Transport-Security: max-age=15552000; preload
Server: cloudflare
CF-RAY: 7876a1948960ca64-HAM
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
DNS Records DNS Resource Records associated with a hostname
View DNS Records