2.4 sec in total
104 ms
2.2 sec
115 ms
Visit capalink.org now to see the best up-to-date Capalink content and also check out these interesting facts you probably never knew about capalink.org
Our trade organization works to improve the family entertainment industry in California. Join our organization that supports amusement parks.
Visit capalink.orgWe analyzed Capalink.org page load time and found that the first response time was 104 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
capalink.org performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value5.7 s
16/100
25%
Value5.7 s
51/100
10%
Value80 ms
99/100
30%
Value0.958
3/100
15%
Value5.9 s
65/100
10%
104 ms
109 ms
809 ms
807 ms
36 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 28% of them (22 requests) were addressed to the original Capalink.org, 58% (46 requests) were made to Assets.myregisteredsite.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (809 ms) relates to the external source Assets.myregisteredsite.com.
Page size can be reduced by 2.3 MB (11%)
21.4 MB
19.1 MB
In fact, the total size of Capalink.org main page is 21.4 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. 50% of websites need less resources to load. Images take 21.1 MB which makes up the majority of the site volume.
Potential reduce by 98.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 98.0 kB or 80% of the original size.
Potential reduce by 2.1 MB
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. Capalink images are well optimized though.
Potential reduce by 101.4 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 101.4 kB or 45% of the original size.
Potential reduce by 5.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. Capalink.org needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 49% of the original size.
Number of requests can be reduced by 44 (67%)
66
22
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capalink. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
capalink.org
104 ms
www.capalink.org
109 ms
jquery.js
809 ms
button.css
807 ms
browserBehavior.js
36 ms
utils.js
45 ms
shared.js
807 ms
navigation.js
51 ms
uaDefaultStylesReset.css
808 ms
popup.js
61 ms
ResourceLoader.js
808 ms
webcom_copyright_kw.js
809 ms
button.css
84 ms
shared.js
101 ms
jquery.js
133 ms
uaDefaultStylesReset.css
101 ms
ResourceLoader.js
105 ms
webcom_copyright_kw.js
107 ms
googleFonts.css
19 ms
css
35 ms
jquery.js
40 ms
navigation.js
18 ms
core.js
19 ms
jqueryvalidate.js
21 ms
photoalbum.js
21 ms
footercontact.js
20 ms
galleria.js
68 ms
lightgallery.js
20 ms
justifiedgallery.js
21 ms
lightslider.js
20 ms
form.js
20 ms
hoverIntent.js
18 ms
bgIframe.js
19 ms
superfish.js
22 ms
handler.js
20 ms
helper.js
21 ms
positioner.js
19 ms
structure.css
35 ms
templates.js
36 ms
defaults.js
37 ms
photoalbum.galleria.io.js
40 ms
photoalbum.light.weight.js
44 ms
photoalbum.css
40 ms
jquery.json-2.2.min.js
55 ms
templates.js
55 ms
footercontact.css
59 ms
utils.js
60 ms
resources.js
59 ms
templates.js
65 ms
form.css
85 ms
form_generic.css
86 ms
sdk.js
15 ms
sdk.js
5 ms
108 ms
129161914.jpg
58 ms
129295962.png
56 ms
129295961.png
57 ms
136386898.png
176 ms
127925177.png
129 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQVIT9d4cw.ttf
75 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf
77 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKibpUVz0Eg.ttf
81 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKibpUVz0Eg.ttf
114 ms
logger.php
141 ms
lightslider.min.css
28 ms
138531071.png
338 ms
138531072.png
358 ms
138531073.png
239 ms
138531074.png
347 ms
138531075.png
295 ms
138531076.png
343 ms
138531077.png
567 ms
138531078.png
616 ms
138531079.png
590 ms
138531082.png
627 ms
138531083.png
632 ms
138531084.png
665 ms
loading.gif
21 ms
logger.php
75 ms
capalink.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
capalink.org 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
Browser errors were logged to the console
capalink.org SEO score
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 Capalink.org 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 Capalink.org 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.
capalink.org
Open Graph description is not detected on the main page of Capalink. 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: