3.8 sec in total
267 ms
2 sec
1.6 sec
Welcome to gonna.do homepage info - get ready to check Gonna best content right away, or after learning these important things about gonna.do
The domain name gonna.do is for sale. Make an offer or buy it now at a set price.
Visit gonna.doWe analyzed Gonna.do page load time and found that the first response time was 267 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
gonna.do performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value16.7 s
0/100
25%
Value6.2 s
44/100
10%
Value5,260 ms
0/100
30%
Value0.33
34/100
15%
Value17.1 s
4/100
10%
267 ms
635 ms
91 ms
104 ms
25 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gonna.do, 52% (27 requests) were made to Gonnado.com and 10% (5 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (635 ms) relates to the external source Gonnado.com.
Page size can be reduced by 722.4 kB (11%)
6.5 MB
5.8 MB
In fact, the total size of Gonna.do main page is 6.5 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. 70% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.
Potential reduce by 24.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 11.1 kB, which is 39% 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 24.1 kB or 85% of the original size.
Potential reduce by 139.4 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. Gonna images are well optimized though.
Potential reduce by 186.5 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 186.5 kB or 63% of the original size.
Potential reduce by 372.5 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. Gonna.do needs all CSS files to be minified and compressed as it can save up to 372.5 kB or 83% of the original size.
Number of requests can be reduced by 26 (59%)
44
18
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gonna. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
gonna.do
267 ms
635 ms
bootstrap.min.css
91 ms
font-awesome.min.css
104 ms
9c7173c11007.css
25 ms
a0a6ae369c11.css
56 ms
w7Wz6bPpd8pyd13RB0xq.js
113 ms
jquery.min.js
145 ms
bootstrap.min.js
120 ms
9b9c1699a884.js
72 ms
logo.png
97 ms
english.png
71 ms
german.png
120 ms
french.png
97 ms
spanish.jpg
137 ms
screen_street.jpg
489 ms
target_blue.png
49 ms
selfmade_icon_yellow.png
47 ms
startup.png
46 ms
partnership_grey.png
48 ms
lab.png
124 ms
website_grey.png
123 ms
customer1.png
122 ms
customer2.png
123 ms
customer3.png
124 ms
customer4.png
131 ms
customer5.png
131 ms
logo-footer.png
130 ms
google_partner.png
131 ms
481 ms
uy5tABaQSlE
178 ms
sourcesanspro-regular.woff
468 ms
sourcesanspro-semibold.woff
367 ms
fontawesome-webfont.woff
10 ms
www-embed-player-vflfNyN_r.css
44 ms
www-embed-player.js
82 ms
base.js
146 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
84 ms
ad_status.js
144 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
128 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
131 ms
fbds.js
194 ms
conversion_async.js
130 ms
jquery-1.11.3.min.js
151 ms
61 ms
20 ms
27 ms
29 ms
85 ms
37 ms
26 ms
4 ms
gonna.do 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
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 valid value for its [lang] attribute.
[lang] attributes do not have a valid value
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
Links do not have a discernible name
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.
gonna.do 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
Page has valid source maps
gonna.do SEO score
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
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gonna.do can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gonna.do main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
gonna.do
Open Graph description is not detected on the main page of Gonna. 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: