Tools & Wizards About Us
foratable.ch screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

foratable.ch

Restaurant Management System - für mehr Erfolg in der Gastronomie

Page Load Speed

773 ms in total

First Response

96 ms

Resources Loaded

599 ms

Page Rendered

78 ms

foratable.ch screenshot

About Website

Welcome to foratable.ch homepage info - get ready to check Foratable best content right away, or after learning these important things about foratable.ch

Ihr Online Partner für Ihr Restaurant. Wir unterstützen Sie mit digitalen Produkten und erhöhen Ihre Online Präsenz.

Visit foratable.ch

Key Findings

We analyzed Foratable.ch page load time and found that the first response time was 96 ms and then it took 677 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

foratable.ch performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value27.0 s

0/100

10%

TBT (Total Blocking Time)

Value14,680 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.104

88/100

15%

TTI (Time to Interactive)

Value33.9 s

0/100

10%

Network Requests Diagram

foratable.ch

96 ms

www.foratable.ch

71 ms

bt

82 ms

require.min.js

55 ms

main-r.min.js

61 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Foratable.ch, 74% (28 requests) were made to Static.parastorage.com and 13% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (350 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (76%)

Content Size

2.5 MB

After Optimization

593.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Foratable.ch main page is 2.5 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. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 13.5 kB

  • Original 17.6 kB
  • After minification 17.4 kB
  • After compression 4.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. 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 13.5 kB or 77% of the original size.

JavaScript Optimization

-76%

Potential reduce by 1.9 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 587.8 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 1.9 MB or 76% of the original size.

CSS Optimization

-77%

Potential reduce by 5.8 kB

  • Original 7.5 kB
  • After minification 6.0 kB
  • After compression 1.7 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. Foratable.ch needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (72%)

Requests Now

36

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foratable.ch

foratable.ch

96 ms

www.foratable.ch

www.foratable.ch

71 ms

bt

bt

82 ms

require.min.js

require.min.js

55 ms

main-r.min.js

main-r.min.js

61 ms

viewer.css

viewer.css

59 ms

dynamicmodel

dynamicmodel

11 ms

08b60e_2f851282292d2d8c11b15d869fc28106_640.json.z

08b60e_2f851282292d2d8c11b15d869fc28106_640.json.z

350 ms

08b60e_2a1729555221942ee42a7ba6127c3e75_637.json.z

08b60e_2a1729555221942ee42a7ba6127c3e75_637.json.z

347 ms

ugc-viewer

ugc-viewer

48 ms

ugc-viewer

ugc-viewer

161 ms

bt

bt

160 ms

skins.min.js

skins.min.js

157 ms

components.min.js

components.min.js

156 ms

utils.min.js

utils.min.js

44 ms

core.min.js

core.min.js

86 ms

react-with-addons.min.js

react-with-addons.min.js

86 ms

lodash.min.js

lodash.min.js

24 ms

TweenMax.min.js

TweenMax.min.js

85 ms

layout.min.js

layout.min.js

153 ms

tpa.min.js

tpa.min.js

151 ms

fonts.min.js

fonts.min.js

86 ms

animations.min.js

animations.min.js

86 ms

swfobject.min.js

swfobject.min.js

153 ms

mousetrap.min.js

mousetrap.min.js

152 ms

tweenEngine.min.js

tweenEngine.min.js

155 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

153 ms

react-dom.min.js

react-dom.min.js

156 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

154 ms

widgets.min.js

widgets.min.js

151 ms

experiment.js

experiment.js

151 ms

render.min.js

render.min.js

154 ms

wixappsCore.min.js

wixappsCore.min.js

155 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

155 ms

zepto.min.js

zepto.min.js

152 ms

color.min.js

color.min.js

152 ms

react-dom-server.min.js

react-dom-server.min.js

124 ms

bt

bt

68 ms

Accessibility Review

foratable.ch accessibility score

89

Accessibility Issues

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

foratable.ch best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

foratable.ch SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foratable.ch can be misinterpreted by Google and other search engines. Our service has detected that German 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 Foratable.ch 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.

Social Sharing Optimization

foratable.ch

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: