2.8 sec in total
291 ms
1.4 sec
1.2 sec
Visit dandelion.to now to see the best up-to-date Dandelion content and also check out these interesting facts you probably never knew about dandelion.to
A configuration publish system build on the top of git filesystem. - GitHub - tengattack/dandelion: A configuration publish system build on the top of git filesystem.
Visit dandelion.toWe analyzed Dandelion.to page load time and found that the first response time was 291 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
dandelion.to performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value5.8 s
15/100
25%
Value8.4 s
18/100
10%
Value5,510 ms
0/100
30%
Value0
100/100
15%
Value11.9 s
16/100
10%
291 ms
507 ms
133 ms
160 ms
262 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Dandelion.to, 96% (45 requests) were made to Github.githubassets.com and 2% (1 request) were made to Github.com. The less responsive or slowest element that took the longest time to load (573 ms) relates to the external source Github.githubassets.com.
Page size can be reduced by 169.9 kB (54%)
314.9 kB
145.0 kB
In fact, the total size of Dandelion.to main page is 314.9 kB. 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. HTML takes 195.9 kB which makes up the majority of the site volume.
Potential reduce by 164.9 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 164.9 kB or 84% of the original size.
Potential reduce by 5.1 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. Dandelion.to has all CSS files already compressed.
Number of requests can be reduced by 43 (96%)
45
2
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dandelion. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
dandelion.to
291 ms
dandelion
507 ms
light-5178aee0ee76.css
133 ms
dark-217d4f9c8e70.css
160 ms
primer-c6f0537b24f5.css
262 ms
global-d59fab330389.css
203 ms
github-84ec6bc96334.css
161 ms
code-3d7b701fc6eb.css
201 ms
wp-runtime-081f32b13638.js
249 ms
vendors-node_modules_manuelpuyol_turbo_dist_turbo_es2017-esm_js-8af9baefab9e.js
380 ms
vendors-node_modules_stacktrace-parser_dist_stack-trace-parser_esm_js-node_modules_github_bro-d351f6-c1d63d230b29.js
380 ms
environment-0688fc283fd4.js
539 ms
vendors-node_modules_selector-observer_dist_index_esm_js-650337916dbd.js
539 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_details-dialog-elemen-63debe-411ad558985a.js
540 ms
vendors-node_modules_fzy_js_index_js-node_modules_github_combobox-nav_dist_index_js-node_modu-344bff-2d497eaa2bcd.js
539 ms
vendors-node_modules_github_file-attachment-element_dist_index_js-node_modules_github_filter--1a5034-4afde803c0f4.js
538 ms
vendors-node_modules_github_tab-container-element_dist_index_js-node_modules_github_auto-comp-d0a479-59a6ec35bd52.js
539 ms
vendors-node_modules_github_time-elements_dist_index_js-74b4ec51ce20.js
542 ms
vendors-node_modules_primer_view-components_app_components_primer_primer_js-node_modules_gith-e7a013-130ddc88f441.js
542 ms
github-elements-4033ee366856.js
527 ms
element-registry-552a06e513f1.js
526 ms
vendors-node_modules_lit-html_lit-html_js-e954e8c01c93.js
524 ms
vendors-node_modules_github_mini-throttle_dist_index_js-node_modules_primer_behaviors_dist_es-899b47-60b74f01ac2c.js
524 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_github_catalyst_lib_index_-bd1f73-6256737c3b34.js
540 ms
vendors-node_modules_github_paste-markdown_dist_index_esm_js-node_modules_koddsson_textarea-c-586f78-aad0fa01c792.js
540 ms
vendors-node_modules_github_alive-client_dist_index_js-node_modules_github_memoize_dist_esm_i-fab77c-ff9d9fde6bc6.js
539 ms
vendors-node_modules_github_filter-input-element_dist_index_js-node_modules_github_quote-sele-2aa7d6-afe9c63dd113.js
539 ms
app_assets_modules_github_updatable-content_ts-62df1309213c.js
539 ms
app_assets_modules_github_sticky-scroll-into-view_ts-6483ace64969.js
542 ms
app_assets_modules_github_behaviors_keyboard-shortcuts-helper_ts-app_assets_modules_github_be-ac2ea2-b917df335cb3.js
544 ms
app_assets_modules_github_behaviors_commenting_edit_ts-app_assets_modules_github_behaviors_ht-83c235-db7959b5fff9.js
543 ms
app_assets_modules_github_behaviors_batch-deferred-content_ts-app_assets_modules_github_behav-dc1370-508b62ad088a.js
543 ms
behaviors-4b07df7d46de.js
572 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_catalyst_lib_index_js-06ff533-ac681f750823.js
542 ms
notifications-global-47ba35d34d1d.js
569 ms
vendors-node_modules_optimizely_optimizely-sdk_dist_optimizely_browser_es_min_js-node_modules-4de5ed-5896dc00fff4.js
573 ms
optimizely-1dce78b124a8.js
571 ms
vendors-node_modules_virtualized-list_es_index_js-node_modules_github_template-parts_lib_index_js-17ccfc4926a4.js
570 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-911b971-6879c2089889.js
460 ms
app_assets_modules_github_ref-selector_ts-71d0dbfd9b78.js
440 ms
codespaces-9de3970c28c5.js
425 ms
vendors-node_modules_github_mini-throttle_dist_decorators_js-node_modules_github_remote-form_-fbd595-666a00cf3b70.js
352 ms
repositories-5f0997963d2c.js
342 ms
topic-suggestions-581480b5d467.js
224 ms
code-menu-87b75537750e.js
255 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-94fd67-0a275c70bcd7.js
255 ms
sessions-9c3520021745.js
97 ms
dandelion.to 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
dandelion.to best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
dandelion.to 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dandelion.to 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 Dandelion.to 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.
dandelion.to
Open Graph data is detected on the main page of Dandelion. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: