5.1 sec in total
1.1 sec
3.8 sec
283 ms
Visit seeds2.co.uk now to see the best up-to-date Seeds 2 content and also check out these interesting facts you probably never knew about seeds2.co.uk
This domain may be for sale!
Visit seeds2.co.ukWe analyzed Seeds2.co.uk page load time and found that the first response time was 1.1 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
seeds2.co.uk performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value3.5 s
62/100
25%
Value3.0 s
94/100
10%
Value310 ms
77/100
30%
Value0.272
45/100
15%
Value3.4 s
93/100
10%
1058 ms
237 ms
156 ms
170 ms
168 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 98% of them (45 requests) were addressed to the original Seeds2.co.uk, 2% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Seeds2.co.uk.
Page size can be reduced by 548.4 kB (15%)
3.7 MB
3.2 MB
In fact, the total size of Seeds2.co.uk main page is 3.7 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. 25% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 20.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. 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 20.1 kB or 80% of the original size.
Potential reduce by 45.5 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. Seeds 2 images are well optimized though.
Potential reduce by 413.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 413.7 kB or 72% of the original size.
Potential reduce by 69.0 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. Seeds2.co.uk needs all CSS files to be minified and compressed as it can save up to 69.0 kB or 83% of the original size.
Number of requests can be reduced by 27 (60%)
45
18
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seeds 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.seeds2.co.uk
1058 ms
style.css
237 ms
colorbox.css
156 ms
jquery.fancybox-1.3.4.css
170 ms
contact.css
168 ms
hoverZoom.css
160 ms
styles.css
168 ms
jquery.js
425 ms
jquery-migrate.min.js
257 ms
html5.js
258 ms
jquery.easing.1.3.js
257 ms
new-slider.js
258 ms
jquery.colorbox-min.js
313 ms
jquery.jcarousel.min.js
322 ms
jquery.fancybox-1.3.4.js
447 ms
jquery.infieldlabel.js
332 ms
jquery.scrollTo-1.4.3.1.js
329 ms
hover.zoom.js
398 ms
jquery-ui-1.8.17.custom.min.js
678 ms
jquery.jqtransform.js
410 ms
script.js
441 ms
js
25 ms
responsive.css
478 ms
comment-reply.min.js
485 ms
jquery.form.min.js
493 ms
scripts.js
502 ms
cufon.js
507 ms
Swiss721_Cn.js
659 ms
wp-emoji-release.min.js
322 ms
style.css
380 ms
slider-loader.gif
80 ms
Fresh-Salad1.jpg
654 ms
Freshly-Baked-Bread.jpg
939 ms
shop-front.jpg
905 ms
image3.jpg
1397 ms
bg.png
88 ms
Seeds-2-Logo-for-Web.png
152 ms
current.png
173 ms
search.png
232 ms
20140214-015740-pm-e1417691044296.jpg
383 ms
Seeds-2-10-300x173.jpg
331 ms
fb.png
412 ms
tw.png
464 ms
border1.png
439 ms
border2.png
497 ms
loading.gif
534 ms
seeds2.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.
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
<frame> or <iframe> elements do not have a title
seeds2.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
seeds2.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 Seeds2.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 Seeds2.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.
seeds2.co.uk
Open Graph description is not detected on the main page of Seeds 2. 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: