3.5 sec in total
350 ms
2.6 sec
572 ms
Welcome to freddysbbq.fr homepage info - get ready to check Freddy S BBQ best content right away, or after learning these important things about freddysbbq.fr
Barbecue Texan en plein coeur de Paris. Dégustez nos viandes longuement fumées dans un décor typiquement américain.
Visit freddysbbq.frWe analyzed Freddysbbq.fr page load time and found that the first response time was 350 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
freddysbbq.fr performance score
name
value
score
weighting
Value11.7 s
0/100
10%
Value28.9 s
0/100
25%
Value14.1 s
1/100
10%
Value1,970 ms
8/100
30%
Value0.002
100/100
15%
Value19.9 s
2/100
10%
350 ms
367 ms
89 ms
179 ms
269 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 63% of them (64 requests) were addressed to the original Freddysbbq.fr, 20% (20 requests) were made to Widget.thefork.com and 15% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Freddysbbq.fr.
Page size can be reduced by 519.9 kB (11%)
4.7 MB
4.2 MB
In fact, the total size of Freddysbbq.fr main page is 4.7 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. 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. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 18.6 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.2 kB, which is 32% 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 18.6 kB or 83% of the original size.
Potential reduce by 435.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. Freddy S BBQ images are well optimized though.
Potential reduce by 55.6 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 55.6 kB or 15% of the original size.
Potential reduce by 10.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. Freddysbbq.fr needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 13% of the original size.
Number of requests can be reduced by 50 (64%)
78
28
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freddy S BBQ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
freddysbbq.fr
350 ms
freddysbbq.fr
367 ms
bootstrap.css
89 ms
settings.css
179 ms
layers.css
269 ms
navigation.css
277 ms
style.css
424 ms
responsive.css
339 ms
logo.png
355 ms
logo-small.png
362 ms
logoabout.png
543 ms
01.jpg
1033 ms
02.jpg
671 ms
03.jpg
614 ms
Drinks.png
1036 ms
Food.png
924 ms
4.png
634 ms
3.png
702 ms
11.png
725 ms
8.png
756 ms
9.png
788 ms
1.png
816 ms
7.png
841 ms
14.png
885 ms
A.png
907 ms
B.png
927 ms
D.png
1029 ms
logoinverse2.png
1032 ms
jquery.js
1033 ms
bootstrap.min.js
1033 ms
jquery.themepunch.revolution.min.js
1053 ms
jquery.themepunch.tools.min.js
1086 ms
revolution.extension.actions.min.js
1092 ms
revolution.extension.carousel.min.js
1096 ms
revolution.extension.kenburn.min.js
1097 ms
revolution.extension.layeranimation.min.js
1110 ms
revolution.extension.migration.min.js
1141 ms
js
55 ms
revolution.extension.navigation.min.js
1178 ms
revolution.extension.parallax.min.js
1102 ms
revolution.extension.slideanims.min.js
1009 ms
revolution.extension.video.min.js
915 ms
main-slider-script.js
928 ms
jquery.fancybox.pack.js
896 ms
jquery.fancybox-media.js
920 ms
owl.js
915 ms
css
31 ms
font-awesome.css
849 ms
animate.css
740 ms
jquery-ui.css
680 ms
owl.css
689 ms
ionicons.css
695 ms
e57e483f-fc7f-4bde-8425-da98bf20fe6d
195 ms
elegend-icons-style.css
658 ms
jquery.fancybox.css
635 ms
appear.js
679 ms
wow.js
889 ms
jquery-ui.js
925 ms
script.js
608 ms
6d22387f4b670103.css
9 ms
22e1d131e7188d20.css
11 ms
polyfills-c67a75d1b6f99dc8.js
96 ms
webpack-31e5220d6987ba81.js
20 ms
framework-bb5c596eafb42b22.js
22 ms
main-c85b995571573cb8.js
22 ms
_app-5999944d2e3eeccb.js
30 ms
ea88be26-ac8001464921255a.js
24 ms
638-e22db868ad5c2348.js
26 ms
460-32c4e83723bda2b6.js
26 ms
689-8e90641e5f41f028.js
26 ms
353-a0c658609419d5db.js
29 ms
%5BrestaurantUuid%5D-5c3acdf29478a633.js
33 ms
_buildManifest.js
43 ms
_ssgManifest.js
29 ms
TF-logo-horizontal.e7fbca04.svg
31 ms
RalewayX_regular.woff
147 ms
RalewayX_light.woff
148 ms
RalewayX_semiBold.woff
147 ms
map-script.js
562 ms
preloader.svg
97 ms
image-1.jpg
417 ms
image-2.jpg
418 ms
image-3.jpg
174 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
18 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
26 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
32 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
38 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
42 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
38 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
51 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
37 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
41 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
52 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
52 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
52 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
53 ms
OpNVnooIhJj96FdB73296ksbOg3F60Y.ttf
66 ms
fontawesome-webfont.woff
144 ms
georgia.woff
95 ms
ionicons.ttf
91 ms
freddysbbq.fr 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
freddysbbq.fr 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
freddysbbq.fr SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freddysbbq.fr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Freddysbbq.fr 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.
freddysbbq.fr
Open Graph description is not detected on the main page of Freddy S BBQ. 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: