Klanten waarvoor wij o.a. gewerkt hebben.
SEO rapport : https://www.matchoffice.de/mieten/business-center/dresden
Volg de aanwijzingen in dit SEO rapport om uw website te optimaliseren voor zoekamchines
onderzocht op : 2023-05-23 11:37:38
SEO Score
pagina titel
Your page title does not exceed 60 characters. It's fine.
SEO info
Lees verder
Meta omschrijving
Je metabeschrijving mag niet langer zijn dan 150 tekens. Het is goed.
SEO info
Meta Keyword
Your site do not have any meta keyword.
SEO info
Enkele trefwoorden
| trefwoord | voorval | Dichtheid | Mogelijke spam |
|---|---|---|---|
| Büro | 8 | 2.797 % | No |
| Sie | 6 | 2.098 % | No |
| Hamburg | 6 | 2.098 % | No |
| Berlin | 6 | 2.098 % | No |
| Center | 5 | 1.748 % | No |
| Coworking | 5 | 1.748 % | No |
| mieten | 5 | 1.748 % | No |
| Köln | 5 | 1.748 % | No |
| Düsseldorf | 4 | 1.399 % | No |
| Business | 4 | 1.399 % | No |
| uns | 4 | 1.399 % | No |
| München | 4 | 1.399 % | No |
| Ihre | 3 | 1.049 % | No |
| Version | 3 | 1.049 % | No |
| Seminarraum | 3 | 1.049 % | No |
| Nutzererfahrung | 3 | 1.049 % | No |
| Office | 3 | 1.049 % | No |
| eine | 3 | 1.049 % | No |
| nutzen | 3 | 1.049 % | No |
| und | 3 | 1.049 % | No |
Twee woordwoordenwoorden
| trefwoord | voorval | Dichtheid | Mogelijke spam |
|---|---|---|---|
| Business Center | 3 | 1.049 % | No |
| Büro mieten | 3 | 1.049 % | No |
| Sie nutzen | 2 | 0.699 % | No |
| um Ihre | 2 | 0.699 % | No |
| Über uns | 2 | 0.699 % | No |
| Coworking Space | 2 | 0.699 % | No |
| mieten Berlin | 2 | 0.699 % | No |
| Office Center | 2 | 0.699 % | No |
| Büro vermieten | 2 | 0.699 % | No |
| Nutzererfahrung zu | 2 | 0.699 % | No |
| Ihre Nutzererfahrung | 2 | 0.699 % | No |
| uns Büro | 2 | 0.699 % | No |
| Frankfurt Stockholmer | 1 | 0.35 % | No |
| Hohenstaufenring 62 | 1 | 0.35 % | No |
| 10117 Berlin | 1 | 0.35 % | No |
| Berlin Speditionstraße | 1 | 0.35 % | No |
| Speditionstraße 21 | 1 | 0.35 % | No |
| München Meetingraum | 1 | 0.35 % | No |
| 21 Düsseldorf | 1 | 0.35 % | No |
| Düsseldorf Ruhrallee | 1 | 0.35 % | No |
Drie woordwoordenwoorden
| trefwoord | voorval | Dichtheid | Mogelijke spam |
|---|---|---|---|
| Ihre Nutzererfahrung zu | 2 | 0.699 % | No |
| uns Büro vermieten | 2 | 0.699 % | No |
| Sie nutzen anscheinend | 1 | 0.35 % | No |
| Thurn und Taxis | 1 | 0.35 % | No |
| und Taxis Platz | 1 | 0.35 % | No |
| Taxis Platz 6 | 1 | 0.35 % | No |
| Platz 6 Frankfurt | 1 | 0.35 % | No |
| 6 Frankfurt Pariser | 1 | 0.35 % | No |
| Frankfurt Pariser Platz | 1 | 0.35 % | No |
| Pariser Platz 6a | 1 | 0.35 % | No |
| Platz 6a 10117 | 1 | 0.35 % | No |
| 6a 10117 Berlin | 1 | 0.35 % | No |
| 10117 Berlin Speditionstraße | 1 | 0.35 % | No |
| Berlin Speditionstraße 21 | 1 | 0.35 % | No |
| Speditionstraße 21 Düsseldorf | 1 | 0.35 % | No |
| 21 Düsseldorf Ruhrallee | 1 | 0.35 % | No |
| Ruhrallee 9 Dortmund | 1 | 0.35 % | No |
| Düsseldorf Ruhrallee 9 | 1 | 0.35 % | No |
| 9 Dortmund Hohenstaufenring | 1 | 0.35 % | No |
| Dortmund Hohenstaufenring 62 | 1 | 0.35 % | No |
Vier woordwoorden
| trefwoord | voorval | Dichtheid | Mogelijke spam |
|---|---|---|---|
| Sie nutzen anscheinend eine | 1 | 0.35 % | No |
| Düsseldorf Ruhrallee 9 Dortmund | 1 | 0.35 % | No |
| Thurn und Taxis Platz | 1 | 0.35 % | No |
| und Taxis Platz 6 | 1 | 0.35 % | No |
| Taxis Platz 6 Frankfurt | 1 | 0.35 % | No |
| Platz 6 Frankfurt Pariser | 1 | 0.35 % | No |
| 6 Frankfurt Pariser Platz | 1 | 0.35 % | No |
| Frankfurt Pariser Platz 6a | 1 | 0.35 % | No |
| Pariser Platz 6a 10117 | 1 | 0.35 % | No |
| Platz 6a 10117 Berlin | 1 | 0.35 % | No |
| 6a 10117 Berlin Speditionstraße | 1 | 0.35 % | No |
| 10117 Berlin Speditionstraße 21 | 1 | 0.35 % | No |
| Berlin Speditionstraße 21 Düsseldorf | 1 | 0.35 % | No |
| Speditionstraße 21 Düsseldorf Ruhrallee | 1 | 0.35 % | No |
| 21 Düsseldorf Ruhrallee 9 | 1 | 0.35 % | No |
| Ruhrallee 9 Dortmund Hohenstaufenring | 1 | 0.35 % | No |
| 106 Fellbach Thurn und | 1 | 0.35 % | No |
| 9 Dortmund Hohenstaufenring 62 | 1 | 0.35 % | No |
| Dortmund Hohenstaufenring 62 Köln | 1 | 0.35 % | No |
| Hohenstaufenring 62 Köln Anckelmannsplatz | 1 | 0.35 % | No |
Gebruik van sleutelwoorden
SEO info
Totaal Woorden
SEO info
Stopwoorden zijn veelvoorkomende woorden, zoals al het voorzetsel, enkele generieke woorden zoals downloaden, klikken, aanbieden, winnen etc. omdat het meest gebruikte trefwoord een kleine factor kan zijn voor bezoekers die u aanmoedigt om meer unieke woorden en m
Tekst / HTML Ratio Test
Tekst / HTML Ratio Test : 2%
SEO info
HTML-headings
H1(0)
H2(0)
H3(0)
H4(0)
H5(0)
H6(0)
h2 status minder belangrijk, maar moet worden gebruikt voor een goed begrip van uw website voor bezoekers.
robot.txt
SEO info
robots.txt is erg belangrijk voor SEO. Uw websitegidsen worden gecrawld en geïndexeerd op de zoekmachine volgens de instructies van de robots.txt. Voeg dus een robots.txt-bestand toe aan de hoofdmap van uw website. Schrijf het goed, inclusief uw met inhoud verrijkte pagina's en andere openbare pagina's en sluit alle pagina's uit die gevoelige informatie bevatten. Onthoud dat de robots.txt-instructie om de toegang tot uw gevoelige informatie op uw pagina te beperken, niet formidabel is op het gebied van beveiligingsredenen voor webpagina's. Gebruik het dus niet voor veiligheidsdoeleinden.
Lees verder
Sitemap
SEO info
Houd ook deze dingen in gedachten:
1) De sitemap moet kleiner zijn dan 10 MB (10.485.760 bytes) en mag maximaal 50.000 url's bevatten. als u meer url's heeft, maakt u meerdere sitemapbestanden en gebruikt u een sitemapindexbestand.
2) Plaats uw sitemap in de hoofdmap van de website en voeg de url van uw sitemap toe aan robots.txt.
3) sitemap.xml kan worden gecomprimeerd met behulp van de grip voor sneller laden.
Verbroken link: een verbroken link is een ontoegankelijke link of URL van een website. een hoger aantal gebroken koppelingen heeft een negatief effect op de ranking van zoekmachines vanwege het verminderde koppelingskapitaal. het heeft ook een slechte impact op de gebruikerservaring. Er zijn verschillende redenen voor een verbroken koppeling. Alle staan hieronder vermeld.
1) Een onjuiste link die u hebt ingevoerd.
2) De bestemmingswebsite heeft de door u verstrekte gelinkte webpagina verwijderd. (Een veel voorkomende 404-fout).
3) De bestemmingswebsite is onherroepelijk verplaatst of bestaat niet meer. (Wijzigen van domein of site geblokkeerd of disfunctioneel).
4) De gebruiker mag zich achter een of andere firewall of soortgelijke software of beveiligingsmechanisme bevinden die de toegang tot de bestemmingswebsite blokkeert.
5) U hebt een link naar een site die wordt geblokkeerd door firewall of soortgelijke software voor externe toegang.
Lees verder
Interne Vs. Externe links
Interne Links
- /privacy
- /
- /favourite_locations
- /mieten
- /mieten/business-center
- /mieten/coworking
- /besprechungs-und-tagungsraeume
- /virtuelle-bueros
- /mieten/buro/berlin
- /mieten/business-center/berlin
- /mieten/coworking/berlin
- /mieten/besprechungsraum/berlin
- /mieten/buro/koln
- /mieten/business-center/koln
- /mieten/coworking/koln
- /mieten/besprechungsraum/koln
- /mieten/buro/hamburg
- /mieten/business-center/hamburg
- /mieten/coworking/hamburg
- /mieten/besprechungsraum/hamburg
- /mieten/buro/duesseldorf
- /mieten/business-center/duesseldorf
- /mieten/coworking/duesseldorf
- /mieten/buro/muenchen
- /mieten/business-center/muenchen
- /mieten/coworking/muenchen
- /mieten/besprechungsraum/muenchen
- /mieten/business-center/frankfurt-innenstadt/mainzer-landstrasse-67743
- /mieten/business-center/stuttgart/stockholmer-platz-51918
- /mieten/coworking/berlin-reinickendorf/breitenbachstrasse-120867
- /mieten/business-center/leipzig/torgauer-strasse-41033
- /mieten/virtual_office/fellbach/stuttgarter-strasse-113164
- /mieten/virtual_office/frankfurt-innenstadt/thurn-und-taxis-platz-52212
- /mieten/business-center/berlin-mitte/pariser-platz-51595
- /mieten/business-center/duesseldorf-medienhafen/speditionstrasse-42374
- /mieten/business-center/dortmund/ruhrallee-52177
- /mieten/business-center/koln-innenstadt/hohenstaufenring-43404
- /mieten/business-center/hamburg-borgfelde/anckelmannsplatz-52271
- /mieten/business-center/berlin-mitte/rahel-hirsch-strasse-44763
- /mieten/business-center/hannover/bahnhofstrasse-42942
- /support
- /ueber-uns
- /fuer-vermieter
- /login
- /favourite_locations
- https://www.matchoffice.de/ueber-uns/membership
- /
- /ueber-uns/kontaktiere-uns
- /fuer-vermieter
- /impressum
- /copyright
- /privacy
- /ssl
Externe links
- https://www.microsoft.com/en-us/edge?form=MA13FJ
- https://www.google.com/intl/en_US/chrome/
- https://www.mozilla.org/en-US/firefox/new/
- https://www.trustpilot.com/review/www.lokalebasen.dk
- mailto:info@matchoffice.com
- https://www.lokalebasen.dk
- https://www.matchoffice.se
- https://www.matchoffice.no
- https://www.matchoffice.fi
- https://www.matchoffice.nl
- https://www.matchoffice.be
- https://www.matchoffice.lu
- https://www.matchoffice.co.uk
- https://www.matchoffice.es
- https://www.matchoffice.fr
- https://www.matchoffice.it
- https://www.matchoffice.at
- https://www.matchoffice.ch
- https://www.matchoffice.com.ua
- https://www.matchoffice.pl
- https://www.matchoffice.hk
- https://www.matchoffice.sg
- https://www.matchoffice.in
- https://www.matchoffice.com
- https://www.facebook.com/MatchOffice
- https://www.linkedin.com/company/matchoffice-aps
Alexa Rank
Domain IP Information
NoIndex, NoFollow, DoDollow Links
NoIndex Links
NoFollow Links
SEO info
NoIndex : De noindex-richtlijn is een metatagwaarde. noindex-richtlijn is om uw website niet te laten zien op de resultaten van zoekmachines. U moet geen noindex instellen als waarde in metatags als u uw website wilt zijn op het resultaat van de zoekmachine.
By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" /> directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).
DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.
By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a> if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.
SEO Friendly Links
Not SEO Friendly Links
- /favourite_locations
- /mieten/virtual_office/fellbach/stuttgarter-strasse-113164
- /mieten/virtual_office/frankfurt-innenstadt/thurn-und-taxis-platz-52212
- /favourite_locations
SEO info
Gebruik deze technieken om dit op te lossen.
1) Vervang onderstrepingsteken of ander scheidingsteken door streepje, schone url door aantal en parameters te schrappen of te vervangen.
2) Marge uw www en non www urls.
3) Gebruik geen dynamische en gerelateerde URL's. Maak een XML-sitemap voor de juiste indexering van de zoekmachine.
4) Blokkeer onvriendelijke en irrelevante links via robots.txt.
5) Onderschrijf je canonieke URL's in canonieke tags.
Lees verder
favicon
Afbeelding 'alt' Test
SEO info
Lees verder
DOC Type
Pagina heeft geen documenttype
SEO info
Lees verder
Afgeschreven HTML-tag
SEO info
HTML-paginaformaat
HTML-paginaformaat is> 100 KB
SEO info
Om uw paginagrootte te verkleinen doet u dit
1) Verplaats alle css en js-code naar een extern bestand.
2) zorg ervoor dat uw tekstinhoud bovenaan de pagina staat, zodat deze kan worden weergegeven voordat de pagina volledig wordt geladen.
3) Verkleinen of comprimeren van alle afbeeldingen, flitsmediabestanden, enz. Zullen beter zijn als deze bestanden kleiner zijn dan 100 KB
Lees verder
GZIP compressie
GZIP-compressie is ingeschakeld. GZIP-gecomprimeerde grootte moet <33KB zijn
SEO info
Inline CSS
SEO info
Interne CSS
SEO info
Micro Data Schema Test
SEO info
Lees verder
IP en DNS-rapport
DNS Report
| SL | Host | Class | TTL | Type | PRI | Target | IP |
| 1 | matchoffice.de | IN | 64 | A | 34.89.196.205 | ||
| 2 | matchoffice.de | IN | 86169 | NS | ns2.dandomain.dk | ||
| 3 | matchoffice.de | IN | 86169 | NS | ns.dandomain.dk | ||
| 4 | matchoffice.de | IN | 86169 | NS | ns3.dandomain.dk | ||
| 5 | www.matchoffice.de | IN | 86164 | CNAME | matchoffice.de | ||
| 6 | matchoffice.de | IN | 86169 | MX | 10 | matchoffice-de.mail.protection.outlook.com |
IP Canonicalization Test
SEO info
Lees verder
URL Canonicalization Test
SEO info
<link rel="canonical" href="https://seocheckpro.nl/seotools" /><link rel="canonical" href="https://www.seocheckpro.nl/seotools" />Beide verwijzen naar de link seocheckpro.nl/seotools. Dus alle verschillende URL's met dezelfde inhoud of pagina komen nu onder de link of url mywebsite.com/home. Dit zal uw positie in de zoekmachines verbeteren door duplicatie van inhoud te elimineren. Gebruik een canonieke tag voor alle dezelfde URL's.
Lees verder
Plain Text Email Test
E-mail lijst met gewone tekst
- info@matchoffice.com
- info@matchoffice.com
- only@1.0.0
SEO info
Om dit te bestrijden, kunt u uw e-mailadressen op verschillende manieren versluieren:
1) CSS-pseudoklassen.
2) Terugblikken op uw e-mailadres.
3) Weergave omkeren met css.
4) Verdoezelen uw e-mailadres met behulp van javascript.
5) Wordpress en php gebruiken (alleen voor WordPress-sites).
Lees verder
CURL Response
| url | https://www.matchoffice.de/mieten/business-center/dresden | content type | text/html; charset=utf-8 |
| http code | 200 | header size | 1347 |
| request size | 201 | filetime | -1 |
| ssl verify result | 0 | redirect count | 0 |
| total time | 1.022694 | namelookup time | 0.004144 |
| connect time | 0.011446 | pretransfer time | 0.030615 |
| size upload | 0 | size download | 144430 |
| speed download | 141225 | speed upload | 0 |
| download content length | -1 | upload content length | 0 |
| starttransfer time | 1.007518 | redirect time | 0 |
| redirect url | primary ip | 34.89.196.205 | |
| certinfo | primary port | 443 | |
| local ip | 136.144.135.144 | local port | 48044 |
PageSpeed Insights (Mobile)
Performance
- Emulated Form Factor Mobile
- Locale En-US
- Category Performance
- Field Data
- First Contentful Paint (FCP) 2215 ms
- FCP Metric Category AVERAGE
- First Input Delay (FID) 15 ms
- FID Metric Category FAST
- Overall Category AVERAGE
- Origin Summary
- First Contentful Paint (FCP) 2215 ms
- FCP Metric Category AVERAGE
- First Input Delay (FID) 15 ms
- FID Metric Category FAST
- Overall Category AVERAGE
- Lab Data
- First Contentful Paint 1.2 s
- First Meaningful Paint 1.2 s
- Speed Index 1.6 s
- First CPU Idle
- Time To Interactive 2.4 s
- Max Potential First Input Delay 170 ms
Audit Data
Keep request counts low and transfer sizes small
58 requests • 1,176 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn More
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
Uses efficient cache policy on static assets
2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
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. Learn More
Total Blocking Time
520 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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. Learn More
Defer offscreen images
Potential savings of 34 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
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. Learn More
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Reduce unused CSS
Potential savings of 22 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Avoids enormous network payloads
Total size was 1,176 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
Minimize main-thread work
3.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
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. Learn More
Avoid an excessive DOM size
2,361 elements
A large DOM will increase memory usage, cause longer Learn More
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn More
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
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. Learn More
PageSpeed Insights (Desktop)
Performance
- Emulated Form Factor Desktop
- Locale En-US
- Category Performance
- Field Data
- First Contentful Paint (FCP) 1693 ms
- FCP Metric Category FAST
- First Input Delay (FID) 3 ms
- FID Metric Category FAST
- Overall Category AVERAGE
- Origin Summary
- First Contentful Paint (FCP) 1693 ms
- FCP Metric Category FAST
- First Input Delay (FID) 3 ms
- FID Metric Category FAST
- Overall Category AVERAGE
- Lab Data
- First Contentful Paint 0.3 s
- First Meaningful Paint 0.3 s
- Speed Index 0.5 s
- First CPU Idle
- Time To Interactive 0.5 s
- Max Potential First Input Delay 70 ms
Audit Data
Keep request counts low and transfer sizes small
59 requests • 1,106 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn More
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
Uses efficient cache policy on static assets
2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
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. Learn More
Total Blocking Time
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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. Learn More
Defer offscreen images
Potential savings of 29 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
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. Learn More
Properly size images
Potential savings of 330 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Reduce unused CSS
Potential savings of 19 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Avoids enormous network payloads
Total size was 1,106 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
Minimizes main-thread work
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
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. Learn More
Avoid an excessive DOM size
2,610 elements
A large DOM will increase memory usage, cause longer Learn More
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn More
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
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. Learn More
