6.8 sec in total
1.8 sec
4 sec
1 sec
Visit wotsforlunchblog.com now to see the best up-to-date Wots For Lunch Blog content and also check out these interesting facts you probably never knew about wotsforlunchblog.com
packed lunches and more
Visit wotsforlunchblog.comWe analyzed Wotsforlunchblog.com page load time and found that the first response time was 1.8 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
wotsforlunchblog.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value7.8 s
3/100
25%
Value16.4 s
0/100
10%
Value180 ms
91/100
30%
Value0
100/100
15%
Value7.9 s
43/100
10%
1806 ms
565 ms
562 ms
557 ms
1088 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 21% of them (21 requests) were addressed to the original Wotsforlunchblog.com, 10% (10 requests) were made to Api-public.addthis.com and 8% (8 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Wotsforlunchblog.com.
Page size can be reduced by 769.2 kB (70%)
1.1 MB
333.8 kB
In fact, the total size of Wotsforlunchblog.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 559.8 kB which makes up the majority of the site volume.
Potential reduce by 187.5 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 187.5 kB or 78% of the original size.
Potential reduce by 12.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. Obviously, Wots For Lunch Blog needs image optimization as it can save up to 12.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 364.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 364.2 kB or 65% of the original size.
Potential reduce by 205.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. Wotsforlunchblog.com needs all CSS files to be minified and compressed as it can save up to 205.0 kB or 83% of the original size.
Number of requests can be reduced by 31 (38%)
82
51
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wots For Lunch Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
wotsforlunchblog.com
1806 ms
wp-emoji-release.min.js
565 ms
style.css
562 ms
app.css
557 ms
commentluv.css
1088 ms
jquery.js
836 ms
jquery-migrate.min.js
553 ms
commentluv.js
1110 ms
cptr.js
12 ms
cptr.js
252 ms
swfobject.js
546 ms
widget.foodieblogroll.com
21 ms
addthis_widget.js
17 ms
output.css
842 ms
zerospam.js
866 ms
wp-embed.min.js
865 ms
cptr.js
162 ms
IMG_20150205_115333.jpg
131 ms
9cb3c7f0bb7411e399630002c9dbaa02_5.jpg
458 ms
6d0d145abb7611e385351280050f592d_5.jpg
491 ms
0087c676bb7711e3aeb00002c9c66724_5.jpg
457 ms
2d6f5fd4bb7a11e3a7af125e731f345f_5.jpg
489 ms
afb64f20bb7a11e39d5d0002c9c7447c_5.jpg
489 ms
I-Made-It-Widget.jpg
769 ms
9875263775_25ac10c061.jpg
454 ms
123e81b2237811e39c8b22000a9f18f4_7.jpg
487 ms
9857961315_13524b648d.jpg
533 ms
9857922145_ff57d39bf8.jpg
535 ms
9858317886_3e18a5c807.jpg
134 ms
bwb-logo_zps1ab0f907.jpg
574 ms
widget.gif
487 ms
d5ebc4f2bb7711e397fa0002c9c757ae_5.jpg
485 ms
88507c04bb7911e3b2d30002c9d8b5ba_5.jpg
722 ms
9808452635_a944c93a14.jpg
531 ms
IMG_20150116_122640.jpg
125 ms
9826060163_e764a174f6.jpg
486 ms
JJS_1577-150x150.jpg
993 ms
JJS_1612-150x150.jpg
1005 ms
JJS_1578-150x150.jpg
1092 ms
JJS_1657-150x150.jpg
1265 ms
fob_2013_logo_home.jpg
565 ms
All-beer-sampling-free.jpg
1075 ms
%C2%A9-I-Made-It-300x184.jpg
996 ms
091f0322bb7b11e38d1b0ee9a8a98a2c_5.jpg
553 ms
Jess-Badge.jpeg
957 ms
7b144f9ebb7811e3919b0e37ec96a7f5_5.jpg
817 ms
ga.js
61 ms
sightings
594 ms
widget.html
64 ms
beacon.js
60 ms
wordpress.png
657 ms
FtiE83li6y8
429 ms
widget1.css
351 ms
Asset_blog_MyKitchenOdissey_160x160.jpg
350 ms
300lo.json
98 ms
counter.aa6b24e16f372c90ce98.js
38 ms
closeit.png
862 ms
__utm.gif
58 ms
sh.953eb77977227bfd253ee158.html
55 ms
200-top.png
48 ms
200-middle_red.png
48 ms
200-footer_red.png
113 ms
quant.js
40 ms
analytics.js
36 ms
shares.json
54 ms
shares.json
48 ms
shares.json
46 ms
shares.json
44 ms
shares.json
49 ms
shares.json
43 ms
shares.json
43 ms
shares.json
44 ms
shares.json
44 ms
shares.json
43 ms
collect
11 ms
collect
100 ms
www-embed-player-vfl-z2BtK.css
29 ms
www-embed-player.js
45 ms
pixel;r=120033647;a=p-0474uJSLcf-62;fpan=1;fpa=P0-184660689-1458812038063;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458812038062;tzo=-180;ref=http%3A%2F%2Fwotsforlunchblog.com%2F;url=http%3A%2F%2Fads.foodieblogroll.com%2Fwidget.html%3FStyleID%3D1%26t%3D1458812036682%26showAd%3D0;ogl=
22 ms
ajaxrequest.js
164 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
38 ms
ad_status.js
39 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
34 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
40 ms
thumb_90.jpg
50 ms
__utm.gif
17 ms
widget-page-load.gif
83 ms
widget-sprites.png
168 ms
thumb_90.jpg
61 ms
thumb_90.jpg
43 ms
thumb_90.jpg
51 ms
thumb_90.jpg
50 ms
thumb_90.jpg
61 ms
thumb_90.jpg
48 ms
thumb_90.jpg
82 ms
nr-100.js
17 ms
bd9c42ad04
47 ms
layers.41190fe1ff0be0c371e0.js
6 ms
wotsforlunchblog.com accessibility score
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
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
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.
wotsforlunchblog.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
Missing source maps for large first-party JavaScript
wotsforlunchblog.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wotsforlunchblog.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 Wotsforlunchblog.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.
wotsforlunchblog.com
Open Graph data is detected on the main page of Wots For Lunch Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: