7 sec in total
894 ms
5.6 sec
556 ms
Visit everyrecipe.co.nz now to see the best up-to-date Everyrecipe content for New Zealand and also check out these interesting facts you probably never knew about everyrecipe.co.nz
Search through 48,000 recipes. With the EveryRecipe.co.nz search engine, you're searching through all the major NZ recipes sites.
Visit everyrecipe.co.nzWe analyzed Everyrecipe.co.nz page load time and found that the first response time was 894 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
everyrecipe.co.nz performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value16.6 s
0/100
25%
Value7.0 s
32/100
10%
Value1,040 ms
26/100
30%
Value0.003
100/100
15%
Value14.1 s
9/100
10%
894 ms
328 ms
666 ms
456 ms
7 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 25% of them (16 requests) were addressed to the original Everyrecipe.co.nz, 43% (27 requests) were made to Static.everyrecipe.co.nz and 8% (5 requests) were made to Delivery.yieldoptimisers.net. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Static.everyrecipe.co.nz.
Page size can be reduced by 346.5 kB (20%)
1.7 MB
1.4 MB
In fact, the total size of Everyrecipe.co.nz main page is 1.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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 46.6 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 46.6 kB or 80% of the original size.
Potential reduce by 20.0 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. Everyrecipe images are well optimized though.
Potential reduce by 203.2 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 203.2 kB or 68% of the original size.
Potential reduce by 76.7 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. Everyrecipe.co.nz needs all CSS files to be minified and compressed as it can save up to 76.7 kB or 79% of the original size.
Number of requests can be reduced by 16 (30%)
53
37
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Everyrecipe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.everyrecipe.co.nz
894 ms
fonts.css
328 ms
mt.css
666 ms
responsive.css
456 ms
analytics.js
7 ms
a.js
244 ms
tag.php
180 ms
tag.php
191 ms
en_NZ-1454984766.js
617 ms
mt-1454984766.js
1139 ms
css
27 ms
img.php
1191 ms
jumbo.jpg
1366 ms
bad-picture.gif
227 ms
img.php
1670 ms
img.php
1755 ms
img.php
2346 ms
img.php
2113 ms
img.php
2359 ms
img.php
2356 ms
img.php
3343 ms
img.php
1990 ms
img.php
2731 ms
img.php
3133 ms
img.php
2817 ms
img.php
2593 ms
img.php
2837 ms
img.php
2831 ms
img.php
2964 ms
img.php
3051 ms
img.php
3063 ms
img.php
3072 ms
img.php
3196 ms
img.php
3285 ms
img.php
3298 ms
img.php
3309 ms
img.php
3361 ms
img.php
3428 ms
img.php
3515 ms
img.php
3533 ms
collect
34 ms
collect
30 ms
beacon.js
26 ms
logo.png
221 ms
ico-s937f30e3b2.png
453 ms
topBlogs.jpg
733 ms
collect
67 ms
ajs.php
194 ms
2A019B_1_0.woff
822 ms
2A019B_0_0.woff
821 ms
2A019B_2_0.woff
874 ms
font
13 ms
fontawesome-webfont.woff
872 ms
1f793414fd9395e09d30188977c53fdb.jpg
487 ms
ajs.php
203 ms
flags-s8e4ae9f695.png
384 ms
sdk.js
26 ms
41 ms
xd_arbiter.php
37 ms
xd_arbiter.php
65 ms
usersync.html
40 ms
usersync.html
26 ms
dsy.php
165 ms
everyrecipe.co.nz 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
everyrecipe.co.nz 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
everyrecipe.co.nz 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Everyrecipe.co.nz can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Everyrecipe.co.nz 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.
everyrecipe.co.nz
Open Graph description is not detected on the main page of Everyrecipe. 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: