5 sec in total
1.1 sec
3.6 sec
326 ms
Welcome to frankieandbennys.com homepage info - get ready to check Frankie And Benny S best content for United Kingdom right away, or after learning these important things about frankieandbennys.com
Your local Frankie & Benny’s restaurant offers feel good food with a big New York, little Italy welcome. Check out our American-inspired menu & book today!
Visit frankieandbennys.comWe analyzed Frankieandbennys.com page load time and found that the first response time was 1.1 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
frankieandbennys.com performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value45.8 s
0/100
25%
Value9.1 s
13/100
10%
Value620 ms
48/100
30%
Value0.143
78/100
15%
Value13.9 s
10/100
10%
1113 ms
325 ms
21 ms
158 ms
164 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 41% of them (57 requests) were addressed to the original Frankieandbennys.com, 23% (32 requests) were made to Static.xx.fbcdn.net and 13% (18 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Frankieandbennys.com.
Page size can be reduced by 933.8 kB (42%)
2.2 MB
1.3 MB
In fact, the total size of Frankieandbennys.com main page is 2.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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 42.1 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 7.0 kB, which is 13% 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 42.1 kB or 76% of the original size.
Potential reduce by 367.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. Obviously, Frankie And Benny S needs image optimization as it can save up to 367.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 337.3 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 337.3 kB or 73% of the original size.
Potential reduce by 187.1 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. Frankieandbennys.com needs all CSS files to be minified and compressed as it can save up to 187.1 kB or 81% of the original size.
Number of requests can be reduced by 61 (47%)
131
70
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frankie And Benny S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
frankieandbennys.com
1113 ms
www.frankieandbennys.com
325 ms
analytics.js
21 ms
css_rEI_5cK_B9hB4So2yZUtr5weuEV3heuAllCDE6XsIkI.css
158 ms
css_O9TVtefiOHCV0aCpOO0b2TtHSEIHvbMpvSdXfxqidVA.css
164 ms
css_a2peDtLi9VfvTpRYnNGp931mc87Sj1nbYSPaw5HwVKU.css
239 ms
css_uodpZ7WyODFYQlbgYg3bGju2wSPreydZloDEyvf2Wis.css
244 ms
js_ytkgDLRBsU6jYxHi4RfdtZaFEahEpiGnRLeJa0vC-bI.js
318 ms
js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js
253 ms
js_FvBWezKhsGxJU-Yi41qvYAlpXctdNNR7mIzff4prZrg.js
253 ms
js_AKk-4PYu8iCsmMD02sjJ2AT-mvN3iNv4W4gyTNXUJ5I.js
399 ms
js_byJm28uC0KJXmSHopEwp3MSWA_cewPFOMQ-jq93LVI0.js
398 ms
collect
24 ms
oct.js
54 ms
pdfobject.js
272 ms
12716873_557934427704970_1520099457_n.jpg
52 ms
tr
162 ms
tr
406 ms
logo_small_r.png
157 ms
tw.png
157 ms
fb.png
152 ms
inst.png
157 ms
mob_soc_icon3.png
153 ms
cookie_close.jpg
148 ms
logo.png
217 ms
faf_link_right_img.png
218 ms
menu_logo.png
218 ms
logo_desktop.png
293 ms
logo_mobile.png
225 ms
logo4.png
296 ms
logo3.png
378 ms
logo.png
301 ms
apple_logo.png
303 ms
android_logo.png
311 ms
tile_breakfast.jpg
466 ms
HP_careers.jpg
569 ms
RAYSOFSUNSHINE_tile_V3_2.jpg
466 ms
HP_TILE_app.jpg
466 ms
tile_lunch.jpg
477 ms
HP_kids.jpg
614 ms
twbottom.jpg
569 ms
i_logo.png
569 ms
t1.png
569 ms
t2.png
570 ms
t3.png
616 ms
t4.png
638 ms
red_i.png
636 ms
12797870_146600162394737_666971920_n.jpg
87 ms
12783900_981166561969581_1469612470_n.jpg
88 ms
12750158_1711940789028574_190423082_n.jpg
91 ms
12751466_1681114055476178_1418836528_n.jpg
89 ms
12677608_104957729895456_1712532703_n.jpg
91 ms
12751301_1044248462280871_1631343363_n.jpg
88 ms
12729702_473657049512186_738562441_n.jpg
92 ms
12717028_855407057915689_551710143_n.jpg
94 ms
12725066_1729145333966143_1783879160_n.jpg
94 ms
12677451_486827408171318_258805504_n.jpg
94 ms
12627891_1290986840927789_1956887415_n.jpg
143 ms
12407597_752201701547321_359133748_n.jpg
142 ms
12558509_1019331134789669_1999057795_n.jpg
140 ms
12424616_1565972973727230_800210108_n.jpg
139 ms
12519313_1564175010572907_1776756932_n.jpg
137 ms
12677172_1652867484977658_851937825_n.jpg
138 ms
12407549_1697510720509912_267355224_n.jpg
148 ms
sdk.js
27 ms
navbg.jpg
1301 ms
user.png
623 ms
menu.png
679 ms
search_white.png
688 ms
arrow_white.png
700 ms
8.jpg
732 ms
but_shadow.png
719 ms
widgets.js
61 ms
aquant.js
41 ms
adsct
122 ms
adsct
95 ms
pixel;r=719965437;a=p-fLuKuGNhwVeuu;orderid=;revenue=;labels=_fp.event.Homepage;fpan=1;fpa=P0-1543862742-1456789356989;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456789356989;tzo=-180;ref=;url=http%3A%2F%2Fwww.frankieandbennys.com%2F;ogl=
23 ms
227 ms
GothaProReg.otf
718 ms
Gotham-Bold_21010.ttf
652 ms
Gotham-Medium.woff
665 ms
twLogo.png
669 ms
instagram.jpg
1173 ms
j.png
731 ms
mpp2.vindicosuite.com
319 ms
xd_arbiter.php
37 ms
xd_arbiter.php
51 ms
twi.png
686 ms
bapi
178 ms
0
76 ms
0
90 ms
load
365 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
124 ms
0
7 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
40 ms
like_box.php
570 ms
jot
86 ms
roNeOY-tz5Y.css
42 ms
UHhaxo8Cs3k.css
43 ms
dbNRhrdsQao.css
75 ms
1ssvpqNRk1L.css
65 ms
O8DK6hTywHD.css
53 ms
QMWjEuGlqGQ.css
74 ms
H-92Cz4DIPN.css
62 ms
_rx8naC75Dy.js
73 ms
x5F9OMjKyLw.js
117 ms
ICDbTSzjQEg.js
112 ms
TTCre3391I0.js
112 ms
njO1TPvGzoR.js
113 ms
b_6HNn_J2BZ.js
113 ms
7cm7D75Y0Sf.js
114 ms
rFmE1g6Dkoz.js
148 ms
W0OV23mIOyO.js
141 ms
hdPYw5PFPz4.js
170 ms
D6JJJzT-tB6.js
141 ms
NPuyGQIfUx-.js
145 ms
JMI5tmJvZMw.js
144 ms
36TdwhIHusi.js
144 ms
DusqSB58d-B.js
188 ms
336JejShbZp.js
191 ms
12705434_10153876828177660_5027326013237011511_n.jpg
121 ms
10347557_10152543804547660_4682501877349315185_n.jpg
99 ms
12672630_10153898497427660_11693218_n.jpg
96 ms
10372583_10153896729982660_8607182978393850670_n.jpg
94 ms
12720113_10153891918742660_33455862_n.jpg
100 ms
12743494_10153889305302660_8502462661829683655_n.jpg
106 ms
12744570_10153882980782660_3951874726005540829_n.jpg
105 ms
wL6VQj7Ab77.png
89 ms
s7jcwEQH7Sx.png
86 ms
l5aPruN9xMM.png
89 ms
QDwYpIaRyfG.png
88 ms
a-ZN6WoEOje.png
88 ms
2.jpg
508 ms
tIFXiEZJgab.js
26 ms
Fl1c2TVhCj-.png
19 ms
I6-MnjEovm5.js
5 ms
vlXaquuXMrr.js
5 ms
collect
10 ms
frankieandbennys.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
Image elements do not have [alt] attributes
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
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.
frankieandbennys.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
frankieandbennys.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 Frankieandbennys.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 Frankieandbennys.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.
frankieandbennys.com
Open Graph description is not detected on the main page of Frankie And Benny S. 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: