Your Website Score is

Similar Ranking

23
دلگرم | مجله اینترنتی و سبک زندگی
delgarm.com
23
INVALID URI: THE HOSTNAME COULD NOT BE PARSED.
techinline.com
23
创业邦 - 帮助创业者成功
cyzone.cn
23
小满科技*以创新科技推进国际贸易
xiaoman.cn
23
الجرس | AL JARAS – نجمة حرة على صدر الصحافة العربية
aljaras.com
23
403 FORBIDDEN
loading-delivery1.com
23
TIZIANA FAUSTI | FASHION AND LUXURY CLOTHING
tizianafausti.com

Latest Sites

19
X-ART ~ BEAUTIFUL EROTICA.
x-art.com
19
LEAST I COULD DO: THE COMIC
leasticoulddo.com
12
TUCSON.COM | BREAKING NEWS | ARIZONA DAILY STAR
tucson.com
14
PREFEITURA DE MAGÉ | A FORÇA DO NOVO É A ENERGIA DO POVO
mage.rj.gov.br
19
HOME - THE BROOKLYNNE NETWORKS
brooklynne.net
14
HOME - ASIA TIMES
asiatimes.com

Top Technologies

Nginx
Web Servers
Google Font API
Font Scripts
Google Tag Manager
Tag Managers
Apache
Web Servers
CloudFlare
CDN
WordPress
CMS
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks

23 wifionice.de Last Updated: 2 weeks

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

Desktop

Mobile

Performance Desktop Score 86%
Best Practices Desktop Score 77%
SEO Desktop Score 90%
Progressive Web App Desktop Score 27%
Performance Mobile Score 43%
Best Practices Mobile Score 69%
SEO Mobile Score 88%
Progressive Web App Mobile Score 30%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 46 Characters
WLAN IM ICE: SO NUTZEN SIE DAS INTERNET IM ZUG
Meta Description 77 Characters
Das neue WLAN im ICE - kostenlos und zuverlässig surfen, mailen oder chatten.
Excerpt Page content
WLAN im ICE: So nutzen Sie das Internet im Zug Zurück Menü Suchen A, ...
Meta Keywords 6 Detected
Keywords Cloud Density
bahn27 wlan20 services13 sparpreis12 login10 bahncard10 angebote10 neue9 europa8 business8
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
bahn 27
wlan 20
services 13
sparpreis 12
login 10
bahncard 10
angebote 10
neue 9
europa 8
business 8
Google Preview Your look like this in google search result
WLAN IM ICE: SO NUTZEN SIE DAS INTERNET IM ZUG
https://www.bahn.de/p/view/service/zug/railnet_ice_bahnhof.shtml
Das neue WLAN im ICE - kostenlos und zuverlässig surfen, mailen oder chatten.
Robots.txt File No Found
Sitemap.xml File No Found
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 1970-01-01 / 50 years
Create on: 1970-01-01 / 50 years
Expires on: 1970-01-01 / 610 months 17 days

IT Service IT Service

Nameservers
ns1.eurodns.com
ns2.eurodns.com
ns3.eurodns.com
ns4.eurodns.com
Page Size Code & Text Ratio
Document Size: ~62.18 KB
Code Size: ~47.96 KB
Text Size: ~14.21 KB Ratio: 22.86%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 65 requests • 1,145 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 34 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 250 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 12.7 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 30 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 95 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 91 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 190 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 2 KB
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 240 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
Total Blocking Time 340 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Defer offscreen images Potential savings of 94 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 15 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.4 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,145 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 9 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 1,769 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 JavaScript Potential savings of 19 KB
Minifying JavaScript files can reduce payload sizes and script parse time

Mobile

Mobile Screenshot
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 30 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 2,190 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 2 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce the impact of third-party code Third-party code blocked the main thread for 830 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
Total Blocking Time 1,210 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 4.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Defer offscreen images Potential savings of 303 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 4.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,325 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 7.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.1 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 10 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 1,768 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 JavaScript Potential savings of 19 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 5.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 62 requests • 1,325 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 32 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 820 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 12.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Page load is not fast enough on mobile networks Interactive at 12.5 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 300 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
First Contentful Paint (3G) 8310 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are not sized appropriately 63% 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
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
Remove unused CSS Potential savings of 94 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 218 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Content-Type: text/html
Server: AmazonS3
x-amz-id-2: ElI3lBSqbK8kM+v6JuiXOPXTnxPUIT2S+aDDxFl2aIQbFUFoXt16Fl5/XtbYO/bG8+L/rX8RqA8=
x-amz-request-id: F1BA94F077F35488
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Cache-Control: max-age=600
Date: Sat, 15 Feb 2020 04:16:02 GMT
Content-Length: 12878
Connection: keep-alive
Content-Security-Policy: default-src 'self' https:; script-src * blob: 'unsafe-inline' 'unsafe-eval' https://*.m-pathy.com; style-src 'self' 'unsafe-inline'; img-src https: data:; font-src 'self' data:; media-src https: http: blob: 'self' hdshlsdbbahn-vh.akamaihd.net; connect-src 'self' https: wss://*.m-pathy.com
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=15768000 ; includeSubDomains ; preload
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments