2.4 sec in total
587 ms
1.7 sec
150 ms
Welcome to drunkenfish.com homepage info - get ready to check Drunken Fish best content for United States right away, or after learning these important things about drunkenfish.com
Voted Best Sushi and Favorite Japanese restaurant year after year, Drunken Fish is the most highly-regarded sushi & Japanese dining experience in St. Louis and Kansas City.
Visit drunkenfish.comWe analyzed Drunkenfish.com page load time and found that the first response time was 587 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
drunkenfish.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value15.7 s
0/100
25%
Value8.6 s
17/100
10%
Value1,100 ms
24/100
30%
Value0.979
2/100
15%
Value16.0 s
6/100
10%
587 ms
31 ms
75 ms
95 ms
95 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Drunkenfish.com, 45% (22 requests) were made to D25bp99q88v7sv.cloudfront.net and 24% (12 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (587 ms) belongs to the original domain Drunkenfish.com.
Page size can be reduced by 277.9 kB (14%)
1.9 MB
1.7 MB
In fact, the total size of Drunkenfish.com main page is 1.9 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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 147.7 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 147.7 kB or 86% of the original size.
Potential reduce by 27 B
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. Drunken Fish images are well optimized though.
Potential reduce by 145 B
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 130.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. Drunkenfish.com needs all CSS files to be minified and compressed as it can save up to 130.0 kB or 82% of the original size.
Number of requests can be reduced by 18 (60%)
30
12
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drunken Fish. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
www.drunkenfish.com
587 ms
a7d137f9-b661-47de-bd31-c15795294f2f.css
31 ms
custom-flex-dccv2.css
75 ms
require.js
95 ms
app2.js
95 ms
js
95 ms
fbevents.js
200 ms
7f61461f-a68d-410a-8b7a-b05b227cc464.png
286 ms
afa622b6-e9a7-4264-a0c1-01c2cc8a15f2_h.jpg
190 ms
7788d1d2-5bd9-447a-8226-9e1594baccb6_h.jpg
190 ms
d5e7c804-1244-45f2-80b0-879705c828ff_h.jpg
190 ms
6d4c3cff-eefc-4522-bb44-c91d097071f8_h.jpg
192 ms
3bb7c821-0a8d-42bc-bbc5-87d394e2a579_h.jpg
352 ms
page.js
57 ms
pjx2vbo.js
169 ms
headerlayout1.js
94 ms
jquery224.js
55 ms
socialprofile.v1.js
141 ms
slider.v1.js
141 ms
valueprop.v1.js
141 ms
customblock.v1.js
140 ms
footer.v1.js
140 ms
js
85 ms
analytics.js
150 ms
Linearicons.ttf
111 ms
fa-v4compatibility.ttf
94 ms
fa-regular-400.ttf
94 ms
fa-brands-400.ttf
109 ms
fa-solid-900.ttf
111 ms
fontawesome-webfont.woff
110 ms
jquery-2.2.4.min.js
84 ms
lozad.js
85 ms
utility.js
243 ms
underscore-1.8.3.js
239 ms
collect
26 ms
d
44 ms
d
121 ms
d
121 ms
d
120 ms
d
164 ms
d
119 ms
d
96 ms
d
163 ms
d
120 ms
d
121 ms
d
298 ms
d
163 ms
collect
22 ms
p.gif
129 ms
drunkenfish.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
drunkenfish.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
drunkenfish.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Drunkenfish.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 Drunkenfish.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.
drunkenfish.com
Open Graph data is detected on the main page of Drunken Fish. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: