3 sec in total
520 ms
2.4 sec
63 ms
Welcome to katiespancakes.com homepage info - get ready to check Katie S Pancakes best content right away, or after learning these important things about katiespancakes.com
Want to have a flippin' good time? Want to have an interactive meal? 'Cause Katie's Pancakes flips 'em and you catch 'em! That's right, we can hit an empty plate at 10 yards with a loaded pancake! Con...
Visit katiespancakes.comWe analyzed Katiespancakes.com page load time and found that the first response time was 520 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
katiespancakes.com performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value7.2 s
5/100
25%
Value6.8 s
34/100
10%
Value1,450 ms
15/100
30%
Value0.009
100/100
15%
Value17.6 s
4/100
10%
520 ms
29 ms
37 ms
37 ms
36 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Katiespancakes.com, 33% (24 requests) were made to Static.wixstatic.com and 25% (18 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 254.2 kB (28%)
923.0 kB
668.8 kB
In fact, the total size of Katiespancakes.com main page is 923.0 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. 80% 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. Javascripts take 385.8 kB which makes up the majority of the site volume.
Potential reduce by 233.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 233.5 kB or 74% of the original size.
Potential reduce by 15.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. Katie S Pancakes images are well optimized though.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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. Katiespancakes.com has all CSS files already compressed.
Number of requests can be reduced by 16 (32%)
50
34
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Katie S Pancakes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
www.katiespancakes.com
520 ms
originTrials.41d7301a.bundle.min.js
29 ms
minified.js
37 ms
focus-within-polyfill.js
37 ms
polyfill.min.js
36 ms
thunderbolt-commons.a475be57.bundle.min.js
28 ms
main.1438a05e.bundle.min.js
98 ms
lodash.min.js
115 ms
react.production.min.js
100 ms
react-dom.production.min.js
102 ms
siteTags.bundle.min.js
114 ms
wix-perf-measure.umd.min.js
129 ms
0e86fc_59a9e136c8c04a14ae2995162d5cb372~mv2.jpg
539 ms
t5lFmMScFUs
189 ms
bundle.min.js
56 ms
0e86fc_8f82df160ebe4fcdafc7330fe96a3e13~mv2.jpg
533 ms
interior-top.png
763 ms
0e86fc_65aa7c7068bd402886e4649e9c15ace1~mv2.png
768 ms
0e86fc_bdb3882768b748eeac2487ce71572f83~mv2.png
828 ms
0e86fc_086c04566fd94cd3917b07cd75418e61~mv2.png
764 ms
0e86fc_f88f71f88b164729b2bb0ca7ef599496~mv2.png
764 ms
0e86fc_955749ff521f450db9264cce8fc4155b~mv2.png
770 ms
0e86fc_7f378ade78b04476a8b416b8e501b8ac~mv2.png
1189 ms
0e86fc_b87e1664055e4b028f9741a052877c32~mv2.png
941 ms
0e86fc_548961b82dc3490db75374b0096ba934~mv2.png
993 ms
0e86fc_4d11747e346d43889180d0651cb7d8e9~mv2.png
1025 ms
0e86fc_52ae21ff1d324e82b04908a1a8524bf3~mv2.png
1069 ms
0e86fc_774bcc7fc6ad4a6397ff0518a2fe1918~mv2.png
1085 ms
0e86fc_01eeab37dda54cbb9fbf34ff0b238887~mv2.png
1177 ms
0e86fc_4980a923190e42d5b1924dc7bb2ee838~mv2.png
1399 ms
0e86fc_53c08a27bf714e19a28f576f3b4ece01~mv2.png
1265 ms
0e86fc_bac1e8799d5940c8986159989c37a54a~mv2.png
1381 ms
0e86fc_97cf5d38b58d45fdbc712825ab672d47~mv2.png
1376 ms
0e86fc_1d085e02cd1e44b3ac59617d3e16e798~mv2_d_1580_1456_s_2.png
1515 ms
0e86fc_b42e6b766a734306aafd68e572c6e724~mv2.png
1397 ms
b2c0a7_9b5ed4da06ba4f40a09243297c346066.png
1271 ms
b2c0a7_b5795d43cfb0457c9a61d0556cd3777d.png
1277 ms
b2c0a7_dce8f55ea08441a2a36986c879f38425.png
1283 ms
113 ms
110 ms
106 ms
134 ms
106 ms
106 ms
331 ms
442 ms
326 ms
324 ms
322 ms
434 ms
www-player.css
11 ms
www-embed-player.js
33 ms
base.js
64 ms
opensans-bold-webfont.woff
31 ms
opensans-regular-webfont.woff
30 ms
ad_status.js
174 ms
jKwdeMg5eTlKLUq1BicdQ3joNHiQFKykZS_8AKWMVTU.js
115 ms
embed.js
49 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
42 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
51 ms
Create
105 ms
id
84 ms
GenerateIT
14 ms
qoe
8 ms
log_event
1 ms
deprecation-en.v5.html
4 ms
bolt-performance
18 ms
deprecation-style.v5.css
4 ms
right-arrow.svg
13 ms
WixMadeforDisplay_W_Bd.woff
4 ms
WixMadeforText_W_Bd.woff
4 ms
WixMadeforText_W_Rg.woff
3 ms
katiespancakes.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Links do not have a discernible 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
katiespancakes.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
katiespancakes.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 Katiespancakes.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 Katiespancakes.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.
katiespancakes.com
Open Graph data is detected on the main page of Katie S Pancakes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: