5.9 sec in total
1.2 sec
4.1 sec
649 ms
Click here to check amazing Aanjal content. Otherwise, check out these important facts you probably never knew about aanjal.de
Herzlich Willkommen im Aanjal - bekannt für indische Spezialitäten im Norden von Berlin (Nähe S- & U-Bhf. Wittenau)
Visit aanjal.deWe analyzed Aanjal.de page load time and found that the first response time was 1.2 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
aanjal.de performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value15.3 s
0/100
25%
Value14.7 s
1/100
10%
Value15,970 ms
0/100
30%
Value0
100/100
15%
Value26.9 s
0/100
10%
1175 ms
8 ms
350 ms
327 ms
336 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 21% of them (24 requests) were addressed to the original Aanjal.de, 18% (21 requests) were made to Maps.googleapis.com and 9% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Aanjal.de.
Page size can be reduced by 1.7 MB (57%)
3.0 MB
1.3 MB
In fact, the total size of Aanjal.de main page is 3.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 30.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 30.3 kB or 77% of the original size.
Potential reduce by 23.5 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. Aanjal images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 67% of the original size.
Potential reduce by 334.5 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. Aanjal.de needs all CSS files to be minified and compressed as it can save up to 334.5 kB or 85% of the original size.
Number of requests can be reduced by 53 (52%)
101
48
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aanjal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.aanjal.de
1175 ms
analytics.js
8 ms
bootstrap.min.css
350 ms
fresco.css
327 ms
res-style-dfcbced046.css
336 ms
jquery.js
506 ms
jquery-migrate.min.js
358 ms
collect
13 ms
fresco.js
464 ms
jquery.backstretch.min.js
377 ms
css
26 ms
css
37 ms
bootstrap.min.js
110 ms
jquery.easing.1.3.js
145 ms
myJS.js
109 ms
aanjal_stock_bg.jpg
535 ms
aanjal_logo.png
124 ms
aanjal_logo_xs.png
120 ms
essen_1-320x205.jpg
223 ms
essen_2-320x205.jpg
174 ms
IMG_5129-320x205.jpg
250 ms
IMG_5132-320x205.jpg
325 ms
IMG_5133-320x205.jpg
249 ms
IMG_5134-320x205.jpg
324 ms
IMG_5135-320x205.jpg
363 ms
IMG_5162-320x205.jpg
326 ms
icon_social_gplus.svg
338 ms
button.js
394 ms
embed
80 ms
G0XvmuebhPCfCq4YdUpRgALUuEpTyoUstqEm5AMlJo4.ttf
47 ms
0XxGQsSc1g4rdRdjJKZrNMDdSZkkecOE1hvV7ZHvhyU.ttf
49 ms
Foydq9xJp--nfYIx2TBz9cBaWKZ57bY3RXgXH6dOjZ0.ttf
101 ms
03aPdn7fFF3H6ngCgAlQzMDdSZkkecOE1hvV7ZHvhyU.ttf
50 ms
QABk9IxT-LFTJ_dQzv7xpCwlidHJgAgmTjOEEzwu1L8.ttf
148 ms
EgBlzoNBIHxNPCMwXaAhYHYhjbSpvc47ee6xR_80Hnw.ttf
49 ms
glyphicons-halflings-regular.woff
420 ms
js
151 ms
init_embed.js
129 ms
widget.js
190 ms
place
722 ms
common.js
23 ms
util.js
50 ms
streetview.js
45 ms
google_white4.png
15 ms
marker.js
39 ms
widget
689 ms
imagery_viewer.js
99 ms
controls.js
15 ms
GeoPhotoService.GetMetadata
89 ms
jquery.min.js
84 ms
underscore-min.js
79 ms
transparent.png
66 ms
css
354 ms
geocoder.js
289 ms
sv4.png
284 ms
openhand_8_8.cur
285 ms
button-tracking
502 ms
mapcnt6.png
40 ms
tmapctrl.png
41 ms
cbk
192 ms
GeoPhotoService.GetMetadata
36 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
35 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
61 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
66 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
72 ms
js
50 ms
map.js
75 ms
google4.png
39 ms
overlay.js
26 ms
onion.js
29 ms
search_impl.js
28 ms
StaticMapService.GetMapImage
230 ms
widget.css
281 ms
widget-en.js
548 ms
stats.js
188 ms
ViewportInfoService.GetViewportInfo
161 ms
ViewportInfoService.GetViewportInfo
220 ms
kh
539 ms
cbk
604 ms
cbk
500 ms
cbk
523 ms
cbk
345 ms
ga.js
713 ms
cbk
710 ms
cbk
712 ms
cbk
871 ms
cbk
506 ms
entity11.png
283 ms
analytics.js
624 ms
vt
434 ms
vt
427 ms
vt
556 ms
vt
556 ms
vt
556 ms
vt
556 ms
vt
556 ms
ViewportInfoService.GetViewportInfo
187 ms
all.js
488 ms
gtm.js
548 ms
__utm.gif
193 ms
ecommerce.js
128 ms
collect
125 ms
collect
103 ms
collect
88 ms
AuthenticationService.Authenticate
83 ms
nr-885.min.js
101 ms
4f26ebb8067f75f50f106f0c.js
101 ms
availability
163 ms
powered_resmio-818x284.png
58 ms
96 ms
xd_arbiter.php
55 ms
879b52250f
136 ms
879b52250f
125 ms
xd_arbiter.php
11 ms
aanjal.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
<frame> or <iframe> elements do not have a title
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.
aanjal.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
Missing source maps for large first-party JavaScript
aanjal.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aanjal.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Aanjal.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.
aanjal.de
Open Graph description is not detected on the main page of Aanjal. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: