11.5 sec in total
2.4 sec
8.8 sec
195 ms
Click here to check amazing Fig And Cherry content. Otherwise, check out these important facts you probably never knew about figandcherry.com
Christie's a born and bred Sydney girl, but has travelled and lived all over the world to get culinary inspiration. Ranked among the Top 30 Australian food
Visit figandcherry.comWe analyzed Figandcherry.com page load time and found that the first response time was 2.4 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
figandcherry.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value12.2 s
0/100
25%
Value17.0 s
0/100
10%
Value350 ms
73/100
30%
Value0
100/100
15%
Value11.1 s
20/100
10%
2439 ms
660 ms
440 ms
40 ms
46 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 62% of them (52 requests) were addressed to the original Figandcherry.com, 12% (10 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Figandcherry.com.
Page size can be reduced by 208.8 kB (31%)
664.2 kB
455.4 kB
In fact, the total size of Figandcherry.com main page is 664.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 363.8 kB which makes up the majority of the site volume.
Potential reduce by 26.8 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 26.8 kB or 77% of the original size.
Potential reduce by 6.1 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. Fig And Cherry images are well optimized though.
Potential reduce by 107.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 107.2 kB or 59% of the original size.
Potential reduce by 68.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. Figandcherry.com needs all CSS files to be minified and compressed as it can save up to 68.7 kB or 81% of the original size.
Number of requests can be reduced by 41 (52%)
79
38
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fig And Cherry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.figandcherry.com
2439 ms
style.css
660 ms
superfish.css
440 ms
jquery.min.js
40 ms
jquery-ui.min.js
46 ms
widget.js
57 ms
plusone.js
65 ms
styles.css
464 ms
wp-paginate.css
455 ms
jquery.js
1147 ms
jquery-migrate.min.js
655 ms
jquery.DDSlider.min.js
686 ms
DDSlider.css
888 ms
dnt7tsu.js
130 ms
all.js
270 ms
widgets.js
143 ms
jquery.form.min.js
677 ms
scripts.js
715 ms
reset.css
668 ms
text.css
709 ms
960.css
912 ms
cb=gapi.loaded_0
35 ms
ga.js
26 ms
mixpanel.2.js
24 ms
bodybg-sq.jpg
468 ms
890000_20pc_horz.jpg
441 ms
logo.jpg
447 ms
fig-banner.gif
456 ms
890000_20pc.jpg
460 ms
down-arrow.jpg
470 ms
style.css
1129 ms
sprite.jpg
906 ms
search_01.png
1446 ms
890000_40pc_hor.jpg
1447 ms
310x250-speltbread.jpg
1133 ms
310x250-bliss-balls.jpg
1161 ms
310x250-zucchinichips.jpg
1576 ms
310x250-smashedavo.jpg
1821 ms
310x250-coffee-pudding.jpg
1836 ms
30bg.jpg
1615 ms
160x110_breakfast.jpg
1892 ms
lil_arrows.jpg
1901 ms
160x110_dinnertime.jpg
2030 ms
160x110_sweettreats.jpg
2084 ms
160x110_vegetarian.jpg
2257 ms
160x110_vegan.jpg
2278 ms
160x110_glutenfree.jpg
2330 ms
win.jpg
2344 ms
160x110_restaurantreviews.jpg
2471 ms
160x110_travelstories.jpg
2521 ms
chia-pikelet-3-50x48.jpg
2711 ms
310x250-kale-bake-50x48.jpg
2737 ms
3849723086_80615890c9_o-50x48.jpg
2788 ms
me-n-pop-50x48.jpg
2797 ms
poppycake3-50x48.jpg
2911 ms
no-knead-bread-11-50x48.jpg
2959 ms
vitasoy.jpg
3837 ms
christie.jpg
3178 ms
morningcopy.png
3224 ms
21 ms
__utm.gif
34 ms
newsletter.jpg
3191 ms
66 ms
count.js
51 ms
xd_arbiter.php
211 ms
xd_arbiter.php
419 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
119 ms
like_box.php
39 ms
hDvwL1_H7g-.css
284 ms
udqjbTyb5Ue.css
352 ms
q68gy-v_YMF.js
486 ms
FJmpeSpHpjS.js
621 ms
0wM5s1Khldu.js
501 ms
1bNoFZUdlYZ.js
501 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
46 ms
info.json
87 ms
%EF%BF%BD
3482 ms
ajax-arrow.jpg
2981 ms
jot
76 ms
297063_10151182846781522_785586182_n.jpg
279 ms
wL6VQj7Ab77.png
74 ms
s7jcwEQH7Sx.png
74 ms
I6-MnjEovm5.js
70 ms
pQrUxxo5oQp.js
136 ms
figandcherry.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
figandcherry.com 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
General
Impact
Issue
Detected JavaScript libraries
figandcherry.com SEO score
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 Figandcherry.com 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 Figandcherry.com 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.
figandcherry.com
Open Graph description is not detected on the main page of Fig And Cherry. 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: