6.3 sec in total
972 ms
4.4 sec
962 ms
Welcome to discovery.ai homepage info - get ready to check Discovery best content right away, or after learning these important things about discovery.ai
Discovery for Marketplaces & Platforms using Artificial Intelligence, Deep Learning, Machine Learning, Graph Data.
Visit discovery.aiWe analyzed Discovery.ai page load time and found that the first response time was 972 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
discovery.ai performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value11.2 s
0/100
25%
Value4.5 s
72/100
10%
Value2,670 ms
4/100
30%
Value0.001
100/100
15%
Value34.7 s
0/100
10%
972 ms
1584 ms
699 ms
73 ms
85 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 84% of them (41 requests) were addressed to the original Discovery.ai, 8% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Discovery.ai.
Page size can be reduced by 583.9 kB (49%)
1.2 MB
598.1 kB
In fact, the total size of Discovery.ai main page is 1.2 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. 45% of websites need less resources to load. Images take 477.7 kB which makes up the majority of the site volume.
Potential reduce by 50.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 38.0 kB, which is 69% 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 50.1 kB or 92% of the original size.
Potential reduce by 37.3 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. Discovery images are well optimized though.
Potential reduce by 268.6 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 268.6 kB or 70% of the original size.
Potential reduce by 227.9 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. Discovery.ai needs all CSS files to be minified and compressed as it can save up to 227.9 kB or 85% of the original size.
Number of requests can be reduced by 28 (65%)
43
15
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discovery. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
discovery.ai
972 ms
bootstrap.min.css
1584 ms
font-awesome.min.css
699 ms
css
73 ms
css
85 ms
retina.min.js
466 ms
hover.min.css
928 ms
owl.carousel.css
485 ms
owl.theme.css
682 ms
owl.transitions.css
715 ms
jquery.fs.wallpaper.css
734 ms
magnific-popup.css
924 ms
spectrum-aqua.css
1372 ms
jquery-1.10.2.js
1292 ms
bootstrap.min.js
997 ms
modernizr.custom.js
737 ms
jquery.easing.1.3.js
738 ms
jquery.fitvids.js
980 ms
jquery.fs.wallpaper.min.js
981 ms
jquery.magnific-popup.min.js
1287 ms
jquery.tubular.1.0.js
1287 ms
owl.carousel.min.js
1287 ms
scrollReveal.js
1288 ms
stellar.js
1414 ms
SmoothScroll.js
1450 ms
jqBootstrapValidation.js
1854 ms
contact_me.js
1688 ms
isotope.pkgd.min.js
1856 ms
spectrum.nav.js
1691 ms
spectrum.js
1691 ms
logo.png
623 ms
demo-bg-1.jpg
947 ms
browser-bar.png
636 ms
demo.gif
2189 ms
faces-demo.jpg
1599 ms
php.png
733 ms
nodejs.png
1181 ms
mobile.png
786 ms
visualstudio.png
985 ms
customer-engagement.png
1250 ms
2.jpg
1196 ms
3.jpg
1448 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
38 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
46 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
267 ms
fontawesome-webfont.woff
1462 ms
PqZhD5HyRPwtzI5fOKmj9J0EAVxt0G0biEntp43Qt6E.ttf
268 ms
analytics.js
79 ms
collect
12 ms
discovery.ai accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
discovery.ai 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
discovery.ai 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discovery.ai 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 Discovery.ai 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.
discovery.ai
Open Graph description is not detected on the main page of Discovery. 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: