Your Website Score is

Similar Ranking

32
CERTIFIED DATA ERASER SOFTWARE FOR PERMANENTLY WIPING DATA
bitraser.com
32
ISTANBUL TOURIST INFORMATION | PLAN, SEE & EXPERIENCE | ISTANBUL TOURIST INFORMATION
istanbul-tourist-information.com
32
GOLD, SILBER & EDELMETALLE SICHER ONLINE KAUFEN UND VERKAUFEN
goldsilbershop.de
31
GESCHICHTE ABITURVORBEREITUNG 2023 - GESCHICHTE KOMPAKT
geschichte-abitur.de
31
STARTSEITE - PFLEGE MIT HERZ - MARKKLEEBERG
pmh-markkleeberg.de
31
MIETWERKSTATT-PORTAL - MIETWERKSTATT IN DEINER NÄHE FINDEN
mietwerkstatt-portal.de
31
AUDAMED GMBH - MEDIZINPRODUKTE
audamed.com

Latest Sites

2
ACHTZIGER-FORUM - PORTAL
achtziger-forum.de
24
ERDZENGEL – GAMING AUS LEIDENSCHAFT
erdzengel.de
26
- WEIHNACHTSKARTENSPRUECHEWEIHNACHTSKARTENSPRUECHE | STIMMUNGSVOLLE SPRÜCHE FÜR KARTEN UND SCRAP BOOKS
weihnachtskartensprueche.de
30
CAFÉ~ELOQUENT – DIE ONLINE KAFFEEPAUSE
cafe-eloquent.de
40
SEO KAOS | KURUMSAL SEO DANIŞMANLIK HIZMETLERI
seokaos.com
3
PRODUKTSUCHMASCHINE - PRODUKTE AUS INTERNET SHOPS FINDEN | MARKTSHOP24.COM
marktshop24.com
41
STERBEKASSE HARDT MÖNCHENGLADBACH
hp-mg.de

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

32 goldsilbershop.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 47%
Best Practices Desktop Score 89%
SEO Desktop Score 100%
Performance Mobile Score 45%
Best Practices Mobile Score 89%
SEO Mobile Score 100%
Page Authority Authority 44%
Domain Authority Domain Authority 38%
Moz Rank 4.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 65 Characters
GOLD, SILBER & EDELMETALLE SICHER ONLINE KAUFEN UND VERKAUFEN
Meta Description 148 Characters
Gold, Silber & Edelmetalle sicher kaufen oder diskret verkaufen bei GoldSilbershop.de ✓ Mehrfach ausgezeichneter Edelmetallhändler(Focus Money).
Effective URL 29 Characters
https://www.goldsilbershop.de
Excerpt Page content
Gold, Silber & Edelmetalle sicher online kaufen und verkaufen ...
Keywords Cloud Density
goldbarren48 gold46 silber38 goldmünzen29 silbermünzen29 unze29 silberbarren25 gramm24 edelmetalle22 ihre20
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
goldbarren 48
gold 46
silber 38
goldmünzen 29
silbermünzen 29
unze 29
silberbarren 25
gramm 24
edelmetalle 22
ihre 20
Google Preview Your look like this in google search result
GOLD, SILBER & EDELMETALLE SICHER ONLINE KAUFEN UND VERK
https://www.goldsilbershop.de
Gold, Silber & Edelmetalle sicher kaufen oder diskret verkaufen bei GoldSilbershop.de ✓ Mehrfach ausgezeichneter Edelmetallhändler(Focus Money).
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~721.64 KB
Code Size: ~380.93 KB
Text Size: ~340.71 KB Ratio: 47.21%

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 Potential savings of 778 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Server Backend Latencies 20 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 20 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
Avoid enormous network payloads Total size was 3,392 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce JavaScript execution time 1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
User Timing marks and measures 7 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Total Blocking Time 390 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests 2 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 an excessive DOM size 4,687 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 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)
Reduce unused CSS Potential savings of 100 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 4.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 4,310 ms
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy 19 resources found
A long cache lifetime can speed up repeat visits to your page
Minimize main-thread work 3.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 17 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 4.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Properly size images Potential savings of 521 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Max Potential First Input Delay 320 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Initial server response time was short Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
Cumulative Layout Shift 0.271
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce the impact of third-party code Third-party code blocked the main thread for 390 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 Potential savings of 40 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Mobile

Mobile Screenshot
Document uses legible font sizes 98.91% 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
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)
Max Potential First Input Delay 320 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint element 19,750 ms
This is the largest contentful element painted within the viewport
Minimize main-thread work 3.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 9.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid serving legacy JavaScript to modern browsers Potential savings of 20 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
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 enormous network payloads Total size was 2,865 KiB
Large network payloads cost users real money and are highly correlated with long load times
User Timing marks and measures 7 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Defer offscreen images Potential savings of 33 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
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
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 the impact of third-party code Third-party code blocked the main thread for 620 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
Reduce JavaScript execution time 1.8 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 2 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
Serve static assets with an efficient cache policy 19 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.01
Cumulative Layout Shift measures the movement of visible elements within the viewport
Properly size images Potential savings of 10 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Eliminate render-blocking resources Potential savings of 600 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Time to Interactive 20.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Reduce unused CSS Potential savings of 101 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 8.4 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce unused JavaScript Potential savings of 778 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Total Blocking Time 460 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint 19.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid an excessive DOM size 4,689 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)
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes

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/2 200 
server: nginx/1.26.3
content-type: text/html; charset=UTF-8
date: Mon, 24 Mar 2025 04:46:01 GMT
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options:
x-content-type-options: nosniff
referrer-policy: strict-origin-when-cross-origin
x-sw-request: frontend;unknown;index;misc;de;frontend;Goldsilbershop
age: 198
cache-control: no-cache, private
content-encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records