Tools & Wizards About Us
facebars.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

facebars.com

facebars.com

Page Load Speed

8.8 sec in total

First Response

2.9 sec

Resources Loaded

5.7 sec

Page Rendered

150 ms

facebars.com screenshot

About Website

Click here to check amazing Facebars content. Otherwise, check out these important facts you probably never knew about facebars.com

Face bars-Face Restaurant, Locations: Face Bangkok, Face Shanghai, Face Jakarta, Face Beijing, Face Pudong.

Visit facebars.com

Key Findings

We analyzed Facebars.com page load time and found that the first response time was 2.9 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

facebars.com performance score

0

Network Requests Diagram

facebars.com

2910 ms

ind_landing.css

448 ms

main.js

462 ms

AC_RunActiveContent.js

465 ms

ind_style.css

226 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 94% of them (30 requests) were addressed to the original Facebars.com, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Facebars.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.8 kB (32%)

Content Size

246.5 kB

After Optimization

168.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Facebars.com main page is 246.5 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. 20% of websites need less resources to load. Images take 178.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 27.6 kB

  • Original 33.0 kB
  • After minification 29.1 kB
  • After compression 5.4 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 3.9 kB, which is 12% 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 27.6 kB or 84% of the original size.

Image Optimization

-20%

Potential reduce by 36.4 kB

  • Original 178.1 kB
  • After minification 141.7 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, Facebars needs image optimization as it can save up to 36.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-29%

Potential reduce by 8.2 kB

  • Original 27.8 kB
  • After minification 24.6 kB
  • After compression 19.7 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 8.2 kB or 29% of the original size.

CSS Optimization

-73%

Potential reduce by 5.6 kB

  • Original 7.6 kB
  • After minification 4.7 kB
  • After compression 2.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. Facebars.com needs all CSS files to be minified and compressed as it can save up to 5.6 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (13%)

Requests Now

31

After Optimization

27

  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facebars. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

facebars.com

facebars.com

2910 ms

ind_landing.css

ind_landing.css

448 ms

main.js

main.js

462 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

465 ms

ind_style.css

ind_style.css

226 ms

ind_topmenu.css

ind_topmenu.css

245 ms

ind_content.css

ind_content.css

247 ms

ind_footer.css

ind_footer.css

432 ms

bg.jpg

bg.jpg

224 ms

landing-top-logo.jpg

landing-top-logo.jpg

462 ms

title-113.jpg

title-113.jpg

233 ms

restaurants-shanghai.png

restaurants-shanghai.png

658 ms

landing-top-shanghai.jpg

landing-top-shanghai.jpg

220 ms

landing-top-jakarta.jpg

landing-top-jakarta.jpg

233 ms

landing-top-pudong.jpg

landing-top-pudong.jpg

436 ms

landing-top-bangkok.jpg

landing-top-bangkok.jpg

664 ms

landing-top-beijing.jpg

landing-top-beijing.jpg

460 ms

landing-top-shanghai-ov.jpg

landing-top-shanghai-ov.jpg

691 ms

landing-top-jakarta-ov.jpg

landing-top-jakarta-ov.jpg

868 ms

landing-top-pudong-ov.jpg

landing-top-pudong-ov.jpg

687 ms

landing-top-bangkok-ov.jpg

landing-top-bangkok-ov.jpg

957 ms

landing-top-beijing-ov.jpg

landing-top-beijing-ov.jpg

872 ms

restaurants-pudong.png

restaurants-pudong.png

1362 ms

restaurants-beijing.png

restaurants-beijing.png

917 ms

restaurants-bangkok.png

restaurants-bangkok.png

1188 ms

restaurants-jakarta.png

restaurants-jakarta.png

1081 ms

bg-mid-y-landning.jpg

bg-mid-y-landning.jpg

1524 ms

landning-top-bg.jpg

landning-top-bg.jpg

1149 ms

title-news-and-promotion.jpg

title-news-and-promotion.jpg

1164 ms

bg-landing-footer.jpg

bg-landing-footer.jpg

1917 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

12 ms

SEO Factors

facebars.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facebars.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Facebars.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

facebars.com

Open Graph description is not detected on the main page of Facebars. 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: