5.5 sec in total
203 ms
4.9 sec
406 ms
Click here to check amazing Caya content. Otherwise, check out these important facts you probably never knew about caya.co.uk
Buy The Caya Single Size, Contoured, Contraceptive Diaphragm In The UK For Safe And Reusable Barrier Contraception.
Visit caya.co.ukWe analyzed Caya.co.uk page load time and found that the first response time was 203 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
caya.co.uk performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value17.6 s
0/100
25%
Value11.0 s
6/100
10%
Value1,330 ms
17/100
30%
Value0.682
8/100
15%
Value20.5 s
2/100
10%
203 ms
1666 ms
168 ms
254 ms
253 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 87% of them (170 requests) were addressed to the original Caya.co.uk, 3% (6 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Caya.co.uk.
Page size can be reduced by 2.6 MB (64%)
4.1 MB
1.5 MB
In fact, the total size of Caya.co.uk main page is 4.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 95.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. 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 95.9 kB or 82% of the original size.
Potential reduce by 81.7 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. Caya images are well optimized though.
Potential reduce by 1.6 MB
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 1.6 MB or 72% of the original size.
Potential reduce by 909.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. Caya.co.uk needs all CSS files to be minified and compressed as it can save up to 909.5 kB or 86% of the original size.
Number of requests can be reduced by 164 (89%)
184
20
The browser has sent 184 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 126 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
caya.co.uk
203 ms
caya.co.uk
1666 ms
calendar.css
168 ms
popup.css
254 ms
button.css
253 ms
style.css
340 ms
gdpr.css
256 ms
styles.css
348 ms
megamenu.css
267 ms
margin-padding.css
342 ms
owl.carousel.css
342 ms
owl.theme.min.css
340 ms
magnific-popup.css
357 ms
animate.css
517 ms
color.css
513 ms
swatches.css
430 ms
promobanners.css
432 ms
owl.carousel.css
441 ms
owl.theme.css
447 ms
animate.min.css
601 ms
style.css
519 ms
whatsapp-chat.css
531 ms
wallets.css
538 ms
trustpilot.min.css
598 ms
bootstrap.min.css
681 ms
font-awesome.css
691 ms
pe-icon-7-stroke.css
621 ms
menu.css
628 ms
theme.css
1012 ms
responsive.css
766 ms
custom.css
711 ms
default.css
718 ms
styles.css
771 ms
style.css
773 ms
grid-mageplaza.css
801 ms
font-awesome.min.css
893 ms
magnific-popup.css
854 ms
font-awesome.min.css
42 ms
js
67 ms
lib.js
335 ms
mgs_brand.css
787 ms
custom_config.css
696 ms
require.js
731 ms
mixins.js
695 ms
requirejs-config.js
696 ms
timer.js
685 ms
bootstrap.js
2 ms
bootstrap.js
737 ms
custom.js
732 ms
jquery.js
222 ms
common.js
127 ms
dataPost.js
127 ms
bootstrap.js
126 ms
app.js
125 ms
form-key-provider.js
124 ms
mage-translation-dictionary.js
222 ms
css
38 ms
js
86 ms
analytics.js
24 ms
jquery-mixin.js
178 ms
hamburger-black.svg
173 ms
caya_logo_180x120_copy_2_1.png
173 ms
efb59018ad150d238bf8042fef861658.png
173 ms
blank.png
239 ms
caya_960x960.png
337 ms
caya_gel_960x960_01_Artboard_1.png
494 ms
DB01A898-86D1-410B-AA1B-B5396091C318.png
266 ms
footer_flag.png
255 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rl.woff
63 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rl.woff
119 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rl.woff
155 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rl.woff
155 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rl.woff
157 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rl.woff
156 ms
collect
104 ms
mage.js
202 ms
Pe-icon-7-stroke.woff
260 ms
domReady.js
256 ms
main.js
258 ms
bootstrap.js
257 ms
template.js
322 ms
confirm.js
326 ms
widget.js
341 ms
types.js
306 ms
layout.js
307 ms
embed.html
86 ms
loading.gif
356 ms
tp.widget.bootstrap.min.js
80 ms
tp.min.js
78 ms
config.js
315 ms
mgs_quickview.js
328 ms
iframeResizer.min.js
332 ms
waypoints.min.js
320 ms
jquery.lazyload.js
373 ms
wrapper.js
380 ms
text.js
385 ms
80000009744.json
242 ms
react.production.min.js
36 ms
react-dom.production.min.js
48 ms
react-is.production.min.js
57 ms
styled-components.min.js
60 ms
embed.js
34 ms
embed.css
17 ms
owl.carousel.min.js
379 ms
fontawesome-webfont.woff
21 ms
fontawesome-webfont.woff
388 ms
fontawesome-webfont.woff
527 ms
quant.js
35 ms
underscore.js
324 ms
knockout.js
342 ms
knockout-es5.js
341 ms
scripts.js
408 ms
engine.js
408 ms
bootstrap.js
447 ms
observable_array.js
447 ms
bound-nodes.js
447 ms
translate.js
384 ms
modal.js
384 ms
main.js
385 ms
registry.js
411 ms
version.js
426 ms
console-logger.js
422 ms
jquery.magnific-popup.min.js
362 ms
js-translation.json
300 ms
caya_homepage_1200x800.png
239 ms
validation.js
138 ms
knockout-repeat.js
143 ms
knockout-fast-foreach.js
142 ms
events.js
163 ms
modal-popup.html
163 ms
modal-slide.html
213 ms
modal-custom.html
226 ms
key-codes.js
227 ms
core.js
243 ms
z-index.js
255 ms
observable_source.js
255 ms
renderer.js
293 ms
resizable.js
309 ms
i18n.js
310 ms
scope.js
328 ms
range.js
339 ms
mage-init.js
340 ms
keyboard.js
379 ms
optgroup.js
388 ms
after-render.js
390 ms
autoselect.js
417 ms
datepicker.js
432 ms
outer_click.js
432 ms
fadeVisible.js
468 ms
collapsible.js
475 ms
staticChecked.js
475 ms
simple-checked.js
508 ms
bind-html.js
518 ms
tooltip.js
518 ms
color-picker.js
550 ms
arrays.js
539 ms
compare.js
523 ms
misc.js
551 ms
objects.js
541 ms
strings.js
540 ms
template.js
518 ms
local.js
517 ms
logger.js
516 ms
entry-factory.js
528 ms
console-output-handler.js
538 ms
formatter.js
523 ms
message-pool.js
511 ms
levels-pool.js
515 ms
logger-utils.js
505 ms
validation.js
525 ms
class.js
527 ms
data.js
527 ms
disable-selection.js
519 ms
focusable.js
517 ms
form.js
519 ms
ie.js
536 ms
keycode.js
546 ms
labels.js
545 ms
jquery-patch.js
518 ms
plugin.js
524 ms
safe-active-element.js
525 ms
safe-blur.js
533 ms
scroll-parent.js
543 ms
tabbable.js
538 ms
unique-id.js
523 ms
loader.js
522 ms
async.js
526 ms
tooltip.html
516 ms
spectrum.js
515 ms
tinycolor.js
515 ms
entry.js
391 ms
moment.js
385 ms
jquery.validate.js
322 ms
dom-observer.js
120 ms
bindings.js
149 ms
jquery.metadata.js
90 ms
caya.co.uk 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 do not have all required [aria-*] attributes
ARIA IDs are not unique
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
caya.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
caya.co.uk 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 Caya.co.uk 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 Caya.co.uk 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.
caya.co.uk
Open Graph data is detected on the main page of Caya. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: