1.9 sec in total
149 ms
1.6 sec
185 ms
Welcome to dandin.me homepage info - get ready to check Dandin best content for Turkey right away, or after learning these important things about dandin.me
{{meta[current_language].description}}
Visit dandin.meWe analyzed Dandin.me page load time and found that the first response time was 149 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
dandin.me performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value14.3 s
0/100
25%
Value7.0 s
33/100
10%
Value860 ms
33/100
30%
Value0.818
4/100
15%
Value11.8 s
17/100
10%
149 ms
16 ms
41 ms
13 ms
15 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 43% of them (23 requests) were addressed to the original Dandin.me, 19% (10 requests) were made to Scontent.cdninstagram.com and 7% (4 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (395 ms) relates to the external source Scontent.cdninstagram.com.
Page size can be reduced by 1.3 MB (66%)
2.0 MB
684.7 kB
In fact, the total size of Dandin.me main page is 2.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. 75% 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 18.1 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 18.1 kB or 72% of the original size.
Potential reduce by 1.3 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. Dandin images are well optimized though.
Potential reduce by 1.1 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.1 MB or 70% of the original size.
Potential reduce by 221.4 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. Dandin.me needs all CSS files to be minified and compressed as it can save up to 221.4 kB or 81% of the original size.
Number of requests can be reduced by 18 (38%)
48
30
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dandin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
dandin.me
149 ms
cloudflare.min.js
16 ms
vendor.b6d7065c.css
41 ms
bootstrap-rtl.0b3d0bab.css
13 ms
main.ea533c8d.css
15 ms
vendor.982adf00.js
69 ms
plugins.acf5bbee.js
70 ms
env.b62ec11f.js
10 ms
app.d32e49ff.js
21 ms
controllers.89eadbdd.js
58 ms
droidarabickufi.css
52 ms
css
66 ms
css
79 ms
DroidKufi-Regular.woff
7 ms
DroidKufi-Bold.woff
143 ms
ga.js
125 ms
sdk.js
310 ms
client.js
145 ms
locale-ar.json
292 ms
362 ms
main-layout.html
210 ms
player.html
142 ms
main.html
223 ms
__utm.gif
29 ms
cb=gapi.loaded_0
20 ms
collect
333 ms
postmessageRelay
294 ms
footer.html
213 ms
header.html
235 ms
%7B%7Binstagram_account.profile_picture%7D%7D
232 ms
%7B%7Bpost.images.low_resolution.url%7D%7D
165 ms
angular-locale_ar.js
155 ms
Material-Design-Iconic-Font.woff
149 ms
fontawesome-webfont.woff
149 ms
170 ms
11355251_453657064795995_1080983192_a.jpg
152 ms
923669_954183081345416_199251625_n.jpg
152 ms
12383472_547929145375590_534571741_n.jpg
182 ms
12728466_982237441852671_983883774_n.jpg
287 ms
12627835_852916904854398_458566981_n.jpg
171 ms
12558361_1130773020266888_1266590965_n.jpg
172 ms
12519205_1506009056369116_299106057_n.jpg
225 ms
12338778_430262583838438_921690076_n.jpg
176 ms
12356352_1661605030764089_944425296_n.jpg
173 ms
12338815_512848452229282_1079499700_n.jpg
395 ms
3193398744-postmessagerelay.js
128 ms
rpc:shindig_random.js
117 ms
dandin-logo-white.png
87 ms
%7B%7BuserModel.profile.user_profile_image%7D%7D
74 ms
dandin-logo-small.png
41 ms
xd_arbiter.php
140 ms
xd_arbiter.php
264 ms
cb=gapi.loaded_0
20 ms
xd_arbiter.php
83 ms
dandin.me accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dandin.me 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
Missing source maps for large first-party JavaScript
dandin.me SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dandin.me can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Arabic. Our system also found out that Dandin.me 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.
dandin.me
Open Graph description is not detected on the main page of Dandin. 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: