8.1 sec in total
2.2 sec
5.7 sec
222 ms
Click here to check amazing Eeda content. Otherwise, check out these important facts you probably never knew about eeda.co.uk
Visit eeda.co.ukWe analyzed Eeda.co.uk page load time and found that the first response time was 2.2 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eeda.co.uk performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value32.1 s
0/100
25%
Value18.1 s
0/100
10%
Value690 ms
43/100
30%
Value0.863
4/100
15%
Value25.0 s
0/100
10%
2158 ms
234 ms
284 ms
561 ms
289 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 79% of them (64 requests) were addressed to the original Eeda.co.uk, 6% (5 requests) were made to Use.fontawesome.com and 6% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Eeda.co.uk.
Page size can be reduced by 971.8 kB (20%)
4.9 MB
3.9 MB
In fact, the total size of Eeda.co.uk main page is 4.9 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. 55% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 80.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 80.9 kB or 82% of the original size.
Potential reduce by 122.8 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. Eeda images are well optimized though.
Potential reduce by 419.9 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 419.9 kB or 52% of the original size.
Potential reduce by 348.3 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. Eeda.co.uk needs all CSS files to be minified and compressed as it can save up to 348.3 kB or 75% of the original size.
Number of requests can be reduced by 61 (86%)
71
10
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eeda. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
www.eeda.co.uk
2158 ms
styles.min.css
234 ms
bootstrap.min.css
284 ms
style.min.css
561 ms
styles.css
289 ms
cookie-law-info-public.css
293 ms
cookie-law-info-gdpr.css
388 ms
jquery.timepicker.min.css
333 ms
fdatepicker.min.css
379 ms
jquery-ui.min.css
482 ms
jquery.autocomplete.css
391 ms
select2.min.css
433 ms
text-security-disc.css
474 ms
eme.css
487 ms
leaflet.css
586 ms
sow-social-media-buttons-atom-02d0bc8d113a.css
532 ms
sow-image-default-113ccd71f3e6.css
572 ms
7e36eb468bea575bc1d7f517a19cf87f.css
579 ms
style.css
586 ms
hero-slider.min.css
629 ms
elementor.min.css
655 ms
siteorigin.min.css
668 ms
all.min.css
772 ms
styles.min.css
779 ms
all.css
26 ms
v4-shims.css
38 ms
jquery.min.js
692 ms
jquery-migrate.min.js
634 ms
cookie-law-info-public.js
660 ms
sow-social-media-buttons-atom-3ac3c07a0bca.css
669 ms
style.css
750 ms
cookie-law-info-table.css
770 ms
elementor.js
776 ms
main.js
777 ms
hooks.min.js
786 ms
i18n.min.js
786 ms
index.js
832 ms
index.js
834 ms
api.js
32 ms
jquery.timepicker.min.js
832 ms
fdatepicker.min.js
737 ms
select2.min.js
795 ms
eme.js
694 ms
core.min.js
738 ms
mouse.min.js
731 ms
resizable.min.js
687 ms
draggable.min.js
681 ms
controlgroup.min.js
695 ms
checkboxradio.min.js
696 ms
button.min.js
686 ms
dialog.min.js
682 ms
functions.min.js
679 ms
scripts.js
740 ms
hero-slider.js
619 ms
so-legacy.js
655 ms
so-legacy-main.min.js
675 ms
wp-polyfill.min.js
675 ms
index.js
678 ms
NFOL-2013-366-resize.jpg
755 ms
Spring-rework.jpg
878 ms
Winter-rework.jpg
888 ms
camping.jpg
505 ms
image.png
801 ms
CCC-Primary-Logo-200px-transparant-inv.png
653 ms
fa-regular-400.woff
27 ms
fa-solid-900.woff
45 ms
fa-brands-400.woff
57 ms
fa-regular-400.woff
564 ms
fa-solid-900.woff
670 ms
fa-brands-400.woff
520 ms
recaptcha__en.js
54 ms
anchor
38 ms
styles__ltr.css
4 ms
recaptcha__en.js
10 ms
PSKopaksc4v0TeE9MSufUBd6uLsTLN3_1JKIESb4JYg.js
32 ms
webworker.js
58 ms
logo_48.png
21 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
44 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
45 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
49 ms
recaptcha__en.js
37 ms
eeda.co.uk 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
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
eeda.co.uk 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
Issues were logged in the Issues panel in Chrome Devtools
eeda.co.uk 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eeda.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 Eeda.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.
eeda.co.uk
Open Graph description is not detected on the main page of Eeda. 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: