11.5 sec in total
312 ms
10.5 sec
663 ms
Visit dotsha.com now to see the best up-to-date Dotsha content and also check out these interesting facts you probably never knew about dotsha.com
Dotsha offers paywalls and subscription management to leading product-led growth business that monetize globally with automated billing
Visit dotsha.comWe analyzed Dotsha.com page load time and found that the first response time was 312 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dotsha.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value6.1 s
12/100
25%
Value16.5 s
0/100
10%
Value930 ms
30/100
30%
Value0.211
59/100
15%
Value18.5 s
3/100
10%
312 ms
3453 ms
581 ms
516 ms
525 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 47% of them (42 requests) were addressed to the original Dotsha.com, 35% (31 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Dotsha.com.
Page size can be reduced by 187.1 kB (26%)
712.4 kB
525.3 kB
In fact, the total size of Dotsha.com main page is 712.4 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. 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. CSS take 268.2 kB which makes up the majority of the site volume.
Potential reduce by 165.2 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 165.2 kB or 86% of the original size.
Potential reduce by 186 B
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. Dotsha images are well optimized though.
Potential reduce by 1.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 20.3 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. Dotsha.com has all CSS files already compressed.
Number of requests can be reduced by 40 (83%)
48
8
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dotsha. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
dotsha.com
312 ms
www.dotsha.com
3453 ms
autoptimize_4f34ff1150b5622687dd6bcce7d68964.css
581 ms
autoptimize_single_4672f30608cef15af5699fd347d56d7c.css
516 ms
autoptimize_single_bc54a1d7e6a01c3573ad352be79b30fa.css
525 ms
autoptimize_single_88c9f7b3fb348b163a73c448a0f2dd45.css
524 ms
pa-frontend-29e7d5b5e.min.css
538 ms
autoptimize_single_6c7fa462ea68e26255963826263d8c85.css
556 ms
autoptimize_single_f4784010289d9cd6ea87fde58f75cd3c.css
1476 ms
autoptimize_single_eaa392f1915965732c15688b0c75483e.css
1477 ms
autoptimize_single_d59c172f63a816ee224cb73b7fabb3f3.css
1539 ms
css
121 ms
jquery.min.js
1596 ms
js
193 ms
css
174 ms
lazysizes.min.js
1478 ms
autoptimize_single_791f143b8053174d91c18d1056d7e556.css
1476 ms
autoptimize_single_9f73e3594e89d5e4b3a2c969e511d4f4.css
1499 ms
autoptimize_single_c2406176b5450f0794ce6766a1a3b8ad.css
1804 ms
autoptimize_single_86244ac6ea7357b76238bc0695a61b49.css
1829 ms
autoptimize_single_bb8dd1768054a8d9c5bf0150ef739576.css
1830 ms
autoptimize_single_6cc979eb3b02f7fce2d8a9a754481bd6.css
1829 ms
regenerator-runtime.min.js
1830 ms
wp-polyfill.min.js
1831 ms
hooks.min.js
1831 ms
i18n.min.js
1832 ms
9113046.js
219 ms
autoptimize_7921ed998e1edfbb056795605a4adcbc.js
1832 ms
wp-emoji-release.min.js
616 ms
gtm.js
359 ms
back-2_v.png
844 ms
map-2.png
673 ms
software_pattern.png
1597 ms
software_icon1.png
1596 ms
software_icon2.png
674 ms
software_icon_2.png
736 ms
software_icon3.png
735 ms
bubble.png
674 ms
bubble_green.png
773 ms
dotsha.png
926 ms
analytics.js
95 ms
js
85 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
896 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
1031 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
1526 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
1626 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
1627 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
1626 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
1626 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
1626 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
1625 ms
elementskit.woff
2092 ms
fa-solid-900.woff
893 ms
fa-solid-900.ttf
1966 ms
fa-regular-400.ttf
1521 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
1629 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
1629 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
1628 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
1629 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
1628 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
1628 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
2086 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
2087 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
2087 ms
S6uyw4BMUTPHjx4wWw.ttf
2087 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
2086 ms
S6u8w4BMUTPHh30AXC-v.ttf
2084 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
2092 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
2090 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf
2093 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3ig.ttf
2093 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTQ3ig.ttf
2090 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf
2090 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTQ3ig.ttf
2093 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf
2095 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf
2093 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTQ3ig.ttf
2092 ms
fa-brands-400.woff
1850 ms
fa-brands-400.ttf
1518 ms
insight.min.js
986 ms
collect
661 ms
collectedforms.js
662 ms
9113046.js
675 ms
conversations-embed.js
674 ms
9113046.js
751 ms
Subscription_SaaS_api_small.png
565 ms
Cotton-quiz_NB.png
564 ms
autoptimize_3950ef1953883cc46c12ed28870e6767.css
164 ms
31 ms
dotsha.com 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
[role]s are not contained by their required parent element
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
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
dotsha.com 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
dotsha.com 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
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dotsha.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Dotsha.com 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.
dotsha.com
Open Graph data is detected on the main page of Dotsha. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: