6.4 sec in total
1.6 sec
4.1 sec
678 ms
Welcome to wafflewindow.com homepage info - get ready to check Waffle Window best content for United States right away, or after learning these important things about wafflewindow.com
Liege Waffles with a Portland Twist
Visit wafflewindow.comWe analyzed Wafflewindow.com page load time and found that the first response time was 1.6 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
wafflewindow.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value8.6 s
1/100
25%
Value7.0 s
32/100
10%
Value490 ms
58/100
30%
Value0.001
100/100
15%
Value8.1 s
42/100
10%
1581 ms
109 ms
146 ms
138 ms
133 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 82% of them (53 requests) were addressed to the original Wafflewindow.com, 6% (4 requests) were made to 0 and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Wafflewindow.com.
Page size can be reduced by 657.6 kB (9%)
7.2 MB
6.6 MB
In fact, the total size of Wafflewindow.com main page is 7.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.4 MB which makes up the majority of the site volume.
Potential reduce by 77.0 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. This page needs HTML code to be minified as it can gain 26.3 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 77.0 kB or 87% of the original size.
Potential reduce by 56.3 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. Waffle Window images are well optimized though.
Potential reduce by 298.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 298.2 kB or 70% of the original size.
Potential reduce by 226.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. Wafflewindow.com needs all CSS files to be minified and compressed as it can save up to 226.0 kB or 86% of the original size.
Number of requests can be reduced by 42 (69%)
61
19
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waffle Window. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
wafflewindow.com
1581 ms
wp-emoji-release.min.js
109 ms
woocommerce-layout.css
146 ms
woocommerce.css
138 ms
testimonial-rotator-style.css
133 ms
font-awesome.min.css
10 ms
style.css
134 ms
css
27 ms
css
38 ms
jquery.js
194 ms
jquery-migrate.min.js
173 ms
jquery.cycletwo.js
201 ms
jquery.cycletwo.addons.js
200 ms
add-to-cart.min.js
197 ms
jquery.blockUI.min.js
198 ms
woocommerce.min.js
239 ms
jquery.cookie.min.js
260 ms
cart-fragments.min.js
266 ms
core.min.js
265 ms
widget.min.js
266 ms
tabs.min.js
268 ms
jquery.easing.min.js
307 ms
jquery.royalslider.min.js
338 ms
jquery.isotope.min.js
338 ms
jquery.loadimages.min.js
312 ms
jquery.fitvids.js
310 ms
jquery.jplayer.min.js
317 ms
jquery.jplayer.playlist.min.js
357 ms
jquery.backstretch.min.js
388 ms
jquery.respond.min.js
416 ms
jquery.touchtouch.min.js
414 ms
jquery.frontend.js
416 ms
comment-reply.min.js
395 ms
wp-embed.min.js
432 ms
style.css
427 ms
HeaderBG.jpg
670 ms
bg-overlay-00050a-90.png
84 ms
twitter.png
85 ms
facebook.png
85 ms
search-light.png
549 ms
IMG_3785-1.jpg
992 ms
pearl-sugar-waffle-platter-1-copy.png
738 ms
Luck-of-the-Irish-Hearththrob-Waffle.jpg
550 ms
Waffle-Window.jpg
553 ms
WaffleWindowShare.jpg
965 ms
Bridgeport-village-coming-soon-copy-480x240.jpg
552 ms
bg-overlay-00050a-50.png
551 ms
Waffle-Email-List-website-signup-copy-1.png
553 ms
TomatoBs-480x240.jpg
552 ms
Mary-ORourke-and-Brendan-Fishback-480x240.jpg
553 ms
controls.png
554 ms
Waffle-Window-LOGO-363x200.png
547 ms
Brick-Background4.jpg
628 ms
bg-the-basics.jpg
545 ms
analytics.js
37 ms
wafflewindow.com
1350 ms
bg-overlay-00050a-95.png
82 ms
loading.gif
104 ms
arrows.png
83 ms
collect
17 ms
IgZJs4-7SA1XX_edsoXWog.ttf
46 ms
chowderhead-webfont.woff
153 ms
CUEdhRk7oC7up0p6t0g4P6uAt5ZXbnuhCpdKjKODxso.ttf
64 ms
collect
80 ms
woocommerce-smallscreen.css
72 ms
wafflewindow.com accessibility score
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
Form elements do not have associated labels
wafflewindow.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
wafflewindow.com 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 Wafflewindow.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 Wafflewindow.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.
wafflewindow.com
Open Graph data is detected on the main page of Waffle Window. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: