24.3 sec in total
347 ms
23 sec
952 ms
Click here to check amazing Delhi6 content. Otherwise, check out these important facts you probably never knew about delhi6.de
Friedrichstraße 237 10969 Berlin, Delhi 6 Berlin, Checkpoint charlie, Delhi 6 Restaurant Berlin, Delhi 6 Restaurant, Indisches Restaurant Berlin, Indian Restaurant Berlin, Beste Restaurant Berlin, Ind...
Visit delhi6.deWe analyzed Delhi6.de page load time and found that the first response time was 347 ms and then it took 23.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
delhi6.de performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value6.5 s
9/100
25%
Value9.5 s
12/100
10%
Value250 ms
84/100
30%
Value0.157
74/100
15%
Value26.2 s
0/100
10%
347 ms
513 ms
130 ms
258 ms
313 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 77% of them (83 requests) were addressed to the original Delhi6.de, 7% (8 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Tripadvisor.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Tripadvisor.com.
Page size can be reduced by 719.3 kB (11%)
6.8 MB
6.1 MB
In fact, the total size of Delhi6.de main page is 6.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 83.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 83.3 kB or 81% of the original size.
Potential reduce by 293.8 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Delhi6 images are well optimized though.
Potential reduce by 321.6 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 321.6 kB or 60% of the original size.
Potential reduce by 20.7 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Delhi6.de needs all CSS files to be minified and compressed as it can save up to 20.7 kB or 22% of the original size.
Number of requests can be reduced by 41 (48%)
85
44
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Delhi6. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
delhi6.de
347 ms
513 ms
wp-emoji-release.min.js
130 ms
jquery.datetimepicker.css
258 ms
slick.css
313 ms
style.css
315 ms
font-awesome.css
316 ms
style.css
325 ms
photobox.css
325 ms
font-awesome.min.css
380 ms
css
60 ms
genericons.css
433 ms
style.css
442 ms
style.css
446 ms
gdpr-main.css
437 ms
jetpack.css
449 ms
jquery.js
696 ms
jquery-migrate.min.js
562 ms
formjquery2.js
552 ms
slick.min.js
622 ms
sb-review.js
558 ms
jquery.datetimepicker.full.js
823 ms
jquery.photobox.js
793 ms
main.js
665 ms
functions.js
677 ms
contact-form.js
729 ms
newsletter-form.js
775 ms
reservation-form.js
786 ms
reviews-form.js
803 ms
devicepx-jetpack.js
56 ms
gprofiles.js
63 ms
wpgroho.js
832 ms
custom_script.js
897 ms
fixto.min.js.js
1224 ms
masonry.min.js
935 ms
jquery.masonry.min.js
910 ms
main.js
955 ms
wp-embed.min.js
938 ms
e-202404.js
60 ms
wejs
19974 ms
wejs
19964 ms
wejs
19904 ms
responsive.css
569 ms
tripadvisor_logo_115x18.gif
233 ms
150_logo-11900-2.png
315 ms
home-header-logo.png
224 ms
d6-loading.gif
256 ms
gb.png
115 ms
de.png
117 ms
delhi6-chai-vintage.jpg
1107 ms
delhi6-gimg-12.jpg
1016 ms
delhi6-gimg-11.jpg
829 ms
delhi6-gimg-10.jpg
819 ms
delhi6-gimg-4.jpg
625 ms
delhi6-gimg-5.jpg
695 ms
delhi6-gimg-6.jpg
1051 ms
delhi6-gimg-7.jpg
1396 ms
delhi6-gimg-13-1.jpg
1531 ms
delhi6-gimg-9.jpg
1586 ms
delhi6-gimg-8.jpg
1669 ms
delhi6-gimg-3.jpg
1346 ms
delhi6-gimg-1-1.jpg
1704 ms
footer-logo.png
1486 ms
map-d6-2.png
1524 ms
CoE2016_WidgetAsset-14348-2.png
88 ms
sdk.js
54 ms
home-header.jpg
1998 ms
freewifi.png
1622 ms
vegan.png
1623 ms
glutenfree.png
1683 ms
nutefree.png
1747 ms
header-border-line-top.png
1744 ms
header-border-left.png
1789 ms
header-border-right.png
1822 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf
43 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr.ttf
71 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf
71 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8RHYOLbOWA.ttf
74 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbfOLbOWA.ttf
72 ms
fontawesome-webfont.woff
1984 ms
dots-back.png
1889 ms
legend-bottom-img.png
1895 ms
DSC_2813.jpg
2760 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkidi18E.ttf
35 ms
6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7psDc.ttf
36 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSdi18E.ttf
37 ms
sdk.js
12 ms
42 ms
logo.png
656 ms
fontawesome-webfont.woff
454 ms
shadow.png
433 ms
fontawesome-webfont.ttf
427 ms
fontawesome-webfont.svg
438 ms
DSC_2783.jpg
1079 ms
shadow.png
353 ms
DSC_2816-1.jpg
1414 ms
footer-back.jpg
464 ms
required.png
340 ms
nunito-v8-latin-700.woff
464 ms
nunito-v8-latin-regular.woff
551 ms
270c.png
101 ms
lity.js
472 ms
admin-ajax.php
846 ms
ajax-loader.gif
474 ms
slick.woff
544 ms
lity.css
115 ms
js
80 ms
platform.js
35 ms
delhi6.de accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
delhi6.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
delhi6.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Delhi6.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Delhi6.de main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
delhi6.de
Open Graph data is detected on the main page of Delhi6. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: