4.8 sec in total
719 ms
3.5 sec
572 ms
Welcome to mytoken.co homepage info - get ready to check MyToken best content right away, or after learning these important things about mytoken.co
Deliver a WOW customer experience with a simple mobile based queue management system.
Visit mytoken.coWe analyzed Mytoken.co page load time and found that the first response time was 719 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mytoken.co performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value10.4 s
0/100
25%
Value8.0 s
21/100
10%
Value1,940 ms
8/100
30%
Value0.291
41/100
15%
Value16.2 s
6/100
10%
719 ms
367 ms
377 ms
572 ms
977 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 78% of them (46 requests) were addressed to the original Mytoken.co, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Ipinfo.io. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Mytoken.co.
Page size can be reduced by 347.7 kB (21%)
1.7 MB
1.3 MB
In fact, the total size of Mytoken.co main page is 1.7 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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 156.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. This page needs HTML code to be minified as it can gain 24.3 kB, which is 13% 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 156.1 kB or 86% of the original size.
Potential reduce by 80.0 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. MyToken images are well optimized though.
Potential reduce by 76.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 76.2 kB or 19% of the original size.
Potential reduce by 35.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. Mytoken.co needs all CSS files to be minified and compressed as it can save up to 35.4 kB or 43% of the original size.
Number of requests can be reduced by 32 (58%)
55
23
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MyToken. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
mytoken.co
719 ms
slick.css
367 ms
aos.css
377 ms
font-awesome.min.css
572 ms
bootstrap.min.css
977 ms
counter.css
377 ms
Index.css
378 ms
style.css
562 ms
sweetalert.css
576 ms
myToken-Price.css
564 ms
slick.css
571 ms
slick-theme.css
746 ms
ScrollBar.css
749 ms
intlTelInput.css
763 ms
javascript.gp
198 ms
api.js
43 ms
sweetalert.min.js
581 ms
sweetalert-dev.js
1063 ms
jquery-3.1.1.min.js
1041 ms
tether.min.js
760 ms
slick.min.js
777 ms
retina.js
772 ms
aos.js
958 ms
bootstrap.min.js
1196 ms
counter.js
977 ms
script.js
1040 ms
jquery-migrate-1.2.1.min.js
12 ms
slick.js
1173 ms
intlTelInput.min.js
1164 ms
css
30 ms
ys7gehpsz388.js
234 ms
analytics.js
106 ms
Facebook-48.png
550 ms
LinkedIn-48.png
550 ms
Twitter-48.png
551 ms
header-bg.jpg
1077 ms
mytoken-logo.png
551 ms
token-announce.png
921 ms
mtl-main.png
1134 ms
create-track-fulfill.png
774 ms
myToken-app.png
974 ms
1.svg
712 ms
2.svg
898 ms
3.svg
963 ms
4.svg
1084 ms
5.svg
1110 ms
6.svg
1152 ms
token-view.png
1897 ms
recaptcha__en.js
72 ms
librefranklin-thin-webfont.woff
1191 ms
fontawesome-webfont5b62.woff
1380 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7gujVj9w.ttf
50 ms
collect
12 ms
collect
110 ms
js
155 ms
ipinfo.io
76 ms
ajax-loader.gif
807 ms
flags.png
823 ms
ipinfo.io
45 ms
mytoken.co 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 input fields do not have accessible names
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
Image elements do not have [alt] attributes
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.
mytoken.co 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
Page has valid source maps
mytoken.co SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Mytoken.co 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 Mytoken.co 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.
mytoken.co
Open Graph description is not detected on the main page of MyToken. 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: