5.7 sec in total
2.2 sec
3.4 sec
175 ms
Click here to check amazing Capnia content for United States. Otherwise, check out these important facts you probably never knew about capnia.com
Visit capnia.comWe analyzed Capnia.com page load time and found that the first response time was 2.2 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
capnia.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value11.7 s
0/100
25%
Value11.2 s
5/100
10%
Value860 ms
33/100
30%
Value1.062
2/100
15%
Value11.6 s
18/100
10%
2171 ms
146 ms
368 ms
250 ms
253 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 98% of them (63 requests) were addressed to the original Capnia.com, 2% (1 request) were made to Piwik.webcontrolcenter.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Capnia.com.
Page size can be reduced by 418.5 kB (77%)
542.9 kB
124.4 kB
In fact, the total size of Capnia.com main page is 542.9 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. 15% of websites need less resources to load. Javascripts take 418.7 kB which makes up the majority of the site volume.
Potential reduce by 52.9 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 8.0 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 52.9 kB or 87% of the original size.
Potential reduce by 191 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. Capnia images are well optimized though.
Potential reduce by 312.7 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 312.7 kB or 75% of the original size.
Potential reduce by 52.8 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. Capnia.com needs all CSS files to be minified and compressed as it can save up to 52.8 kB or 86% of the original size.
Number of requests can be reduced by 49 (78%)
63
14
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capnia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
capnia.com
2171 ms
module.css
146 ms
default.css
368 ms
skin.css
250 ms
portal.css
253 ms
jquery.min.js
473 ms
TabStrip.Default.css
292 ms
RibbonBar.Default.css
289 ms
TabStrip.Default.css
329 ms
WebResource.axd
433 ms
dnncore.js
308 ms
spmenu.js
550 ms
ScriptResource.axd
432 ms
ScriptResource.axd
377 ms
dnn.js
397 ms
dnn.xml.js
448 ms
dnn.xml.jsparser.js
468 ms
dnn.xmlhttp.js
496 ms
dnn.xmlhttp.jsxmlhttprequest.js
488 ms
containers.css
464 ms
initWidgets.js
389 ms
menu_cor1.gif
137 ms
menu_cor2.gif
167 ms
spacer.gif
151 ms
spacer.gif
185 ms
shadow1.gif
186 ms
blue_crn1.gif
202 ms
blue_crn2.gif
201 ms
cor1.gif
221 ms
cor2.gif
223 ms
inner_cor1.gif
243 ms
inner_cor2.gif
254 ms
inner_right.gif
279 ms
img3.gif
290 ms
inner_left.gif
295 ms
spacer.gif
293 ms
neoforce.gif
327 ms
jens.gif
330 ms
img1.gif
361 ms
cor3.gif
360 ms
cor4.gif
364 ms
title_cor1.gif
378 ms
bullet.png
403 ms
title_cor2.gif
401 ms
index.html
299 ms
but_bg.jpg
287 ms
top_bg.gif
289 ms
rightsidebg.gif
302 ms
inner_topbg.gif
178 ms
inner_bg.gif
170 ms
leftsidebg.gif
310 ms
bottom_bg.gif
311 ms
title_bg.gif
344 ms
fottter_bg.gif
353 ms
DotNetNukeAjaxShared.js
350 ms
spacer.gif
356 ms
but_sep.jpg
372 ms
menu_down.gif
373 ms
link_R.gif
399 ms
link_L.gif
407 ms
link_bg1.gif
412 ms
breadcrumb.gif
426 ms
piwik.js
353 ms
widgets.js
99 ms
capnia.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
[role] values are not valid
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
<frame> or <iframe> elements do not have a title
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
capnia.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
capnia.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 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 Capnia.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 Capnia.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.
capnia.com
Open Graph description is not detected on the main page of Capnia. 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: