2.1 sec in total
191 ms
788 ms
1.1 sec
Welcome to da.sh homepage info - get ready to check DA best content for Guatemala right away, or after learning these important things about da.sh
Visit da.shWe analyzed Da.sh page load time and found that the first response time was 191 ms and then it took 1.9 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.
da.sh performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value13.9 s
0/100
25%
Value10.0 s
9/100
10%
Value860 ms
33/100
30%
Value0
100/100
15%
Value20.8 s
2/100
10%
191 ms
11 ms
6 ms
38 ms
9 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 74% of them (45 requests) were addressed to the original Da.sh, 13% (8 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (335 ms) belongs to the original domain Da.sh.
Page size can be reduced by 584.9 kB (15%)
3.8 MB
3.2 MB
In fact, the total size of Da.sh main page is 3.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. 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. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 31.6 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. This page needs HTML code to be minified as it can gain 14.1 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.6 kB or 83% of the original size.
Potential reduce by 5.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. DA images are well optimized though.
Potential reduce by 364.2 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 364.2 kB or 67% of the original size.
Potential reduce by 183.6 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. Da.sh needs all CSS files to be minified and compressed as it can save up to 183.6 kB or 82% of the original size.
Number of requests can be reduced by 8 (16%)
51
43
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
da.sh
191 ms
styles.min.css
11 ms
custom.css
6 ms
jquery.min.js
38 ms
ytplayer.min.js
9 ms
css
91 ms
libraries.min.js
88 ms
scripts.js
82 ms
analytics.js
323 ms
recorder.js
323 ms
DashLogo_white.svg
295 ms
logo-dark.png
297 ms
home15.jpg
298 ms
logo-light-left.png
299 ms
methodology_icons-01.svg
300 ms
methodology_icons-06.svg
303 ms
methodology_icons-02.svg
305 ms
methodology_icons-03.svg
308 ms
methodology_icons-04.svg
310 ms
methodology_icons-05.svg
313 ms
cover11.jpg
331 ms
app9.jpg
335 ms
intro1.jpg
326 ms
l1.png
316 ms
l2.png
315 ms
l3.png
316 ms
l4.png
314 ms
l5.png
313 ms
l6.png
314 ms
l7.png
315 ms
l8.png
316 ms
capital-t-1.jpg
315 ms
capital-t-2.jpg
320 ms
capital-t-4.jpg
324 ms
capital-t-5.jpg
314 ms
capital-t-6.jpg
315 ms
capital-t-8.jpg
316 ms
capital-t-9.jpg
317 ms
capital-t-10.jpg
327 ms
capital-t-11.jpg
326 ms
capital-t-12.jpg
326 ms
capital-t-15.jpg
323 ms
capital-t-14.jpg
323 ms
iframe_api
173 ms
close.png
155 ms
loading.gif
118 ms
prev.png
117 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
152 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
153 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
163 ms
RJMlAoFXXQEzZoMSUteGWKCWcynf_cDxXwCLxiixG1c.ttf
163 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
187 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
162 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
162 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
160 ms
themify.woff
100 ms
next.png
133 ms
collect
86 ms
recorder_web_worker.js
63 ms
collect
83 ms
www-widgetapi.js
54 ms
da.sh accessibility score
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
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
Form elements do not have associated labels
Links do not have a discernible name
da.sh 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
da.sh 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Da.sh 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 Da.sh 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.
da.sh
Open Graph description is not detected on the main page of DA. 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: