1.2 sec in total
273 ms
793 ms
149 ms
Click here to check amazing Dotgo content for Nigeria. Otherwise, check out these important facts you probably never knew about dotgo.com
World's First and Only Open and Global Directory of RCS and WhatsApp Bots
Visit dotgo.comWe analyzed Dotgo.com page load time and found that the first response time was 273 ms and then it took 942 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
dotgo.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value5.5 s
19/100
25%
Value7.1 s
31/100
10%
Value680 ms
43/100
30%
Value0.369
29/100
15%
Value12.9 s
13/100
10%
273 ms
13 ms
13 ms
21 ms
31 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 88% of them (53 requests) were addressed to the original Dotgo.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (273 ms) belongs to the original domain Dotgo.com.
Page size can be reduced by 310.1 kB (51%)
608.7 kB
298.6 kB
In fact, the total size of Dotgo.com main page is 608.7 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. 45% of websites need less resources to load. Images take 311.9 kB which makes up the majority of the site volume.
Potential reduce by 17.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 5.4 kB, which is 25% 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 17.1 kB or 80% of the original size.
Potential reduce by 103.8 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. Obviously, Dotgo needs image optimization as it can save up to 103.8 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 152.9 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 152.9 kB or 66% of the original size.
Potential reduce by 36.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. Dotgo.com needs all CSS files to be minified and compressed as it can save up to 36.3 kB or 82% of the original size.
Number of requests can be reduced by 31 (53%)
58
27
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dotgo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
dotgo.com
273 ms
reset-fonts.css
13 ms
screen.css
13 ms
default.css
21 ms
jquery-1.3.2.min.js
31 ms
scripts.js
16 ms
twitter.js
20 ms
jquery.scrollTo-min.js
16 ms
jquery.cookie.js
17 ms
jquery.hoverIntent.minified.js
16 ms
jquery.corner.js
20 ms
cufon-yui.js
21 ms
Avenir-Demi_600.font.js
21 ms
dotgo.js
19 ms
jquery.qtip-1.0.0-rc3.min.js
44 ms
tooltip.js
19 ms
CalendarPopup.js
21 ms
simulator.js
19 ms
externalLinks.js
41 ms
toggle.js
20 ms
jcarousellite_1.0.1.min.js
20 ms
sticky-bg.png
27 ms
ga.js
56 ms
widgets.js
84 ms
headerWrap-tile.gif
12 ms
head-bkg.jpg
15 ms
head-logo.png
10 ms
topNav-divider.gif
11 ms
nav-users.png
10 ms
nav-publishers.png
10 ms
nav-advertisers.png
12 ms
nav-developers.png
11 ms
nav-support.png
12 ms
nav-blog.png
11 ms
nav-myaccount.png
31 ms
hero4.png
39 ms
more_blue.gif
28 ms
check.gif
27 ms
users.gif
29 ms
publishers.gif
28 ms
developers.gif
28 ms
divider-vert-top.jpg
29 ms
divider-vert-midTile.jpg
30 ms
divider-vert-bottom.jpg
30 ms
logo_wheaties.gif
30 ms
logo_yahoo.png
31 ms
logo_gm.gif
31 ms
logo_blirp.gif
32 ms
icon_fb.gif
32 ms
icon_tumblr.gif
32 ms
icon_google.gif
32 ms
icon_rss.gif
32 ms
footer-bg-tile.gif
33 ms
foot-logo.png
33 ms
foot-divider.gif
34 ms
__utm.gif
14 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
133 ms
dotgo.json
106 ms
syndication
100 ms
357900283482865664
208 ms
dotgo.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
[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
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
dotgo.com 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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
dotgo.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 doesn't use 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 Dotgo.com 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 Dotgo.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.
dotgo.com
Open Graph description is not detected on the main page of Dotgo. 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: