12.7 sec in total
2.3 sec
9.9 sec
519 ms
Click here to check amazing What The Fork content. Otherwise, check out these important facts you probably never knew about whatthefork.co.uk
What The Fork are the only online ordering system for restaurants and takeaways with table ordering that provide a capped cost feature.
Visit whatthefork.co.ukWe analyzed Whatthefork.co.uk page load time and found that the first response time was 2.3 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
whatthefork.co.uk performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value22.4 s
0/100
25%
Value12.8 s
3/100
10%
Value3,380 ms
2/100
30%
Value0.245
51/100
15%
Value28.3 s
0/100
10%
2303 ms
338 ms
345 ms
390 ms
359 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 72% of them (96 requests) were addressed to the original Whatthefork.co.uk, 15% (20 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Snap.licdn.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Whatthefork.co.uk.
Page size can be reduced by 253.8 kB (12%)
2.2 MB
1.9 MB
In fact, the total size of Whatthefork.co.uk 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. 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 203.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. 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 203.4 kB or 81% of the original size.
Potential reduce by 31.8 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. What The Fork images are well optimized though.
Potential reduce by 10.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 8.3 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. Whatthefork.co.uk has all CSS files already compressed.
Number of requests can be reduced by 89 (82%)
108
19
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What The Fork. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
whatthefork.co.uk
2303 ms
formidableforms.css
338 ms
frontend.min.css
345 ms
mediaelementplayer-legacy.min.css
390 ms
wp-mediaelement.min.css
359 ms
styles.css
362 ms
contact-form-7-main.min.css
487 ms
slick.min.css
699 ms
slick-theme.min.css
669 ms
exad-style.min.css
697 ms
woocommerce-layout.min.css
691 ms
woocommerce.min.css
715 ms
font-awesome.min.css
755 ms
prettyPhoto.css
931 ms
style.css
963 ms
astra-addon-65d735b4d8cb38-23093318.css
954 ms
elementor-icons.min.css
989 ms
frontend.min.css
816 ms
swiper.min.css
1084 ms
post-7572.css
1191 ms
frontend.min.css
1323 ms
global.css
1284 ms
post-6713.css
1085 ms
post-3763.css
1342 ms
post-5722.css
1422 ms
post-6080.css
1412 ms
general.min.css
1526 ms
css
53 ms
fontawesome.min.css
1610 ms
regular.min.css
1685 ms
solid.min.css
1698 ms
brands.min.css
1811 ms
jquery.min.js
1820 ms
jquery-migrate.min.js
1856 ms
jquery.blockUI.min.js
2027 ms
add-to-cart.min.js
2068 ms
js.cookie.min.js
2067 ms
s-202410.js
42 ms
js
107 ms
5139711.js
88 ms
e-202410.js
15 ms
animations.min.css
2171 ms
photoswipe.min.css
1944 ms
default-skin.min.css
1955 ms
woocommerce.min.js
2089 ms
jquery.prettyPhoto.min.js
2109 ms
frontend.min.js
2050 ms
index.js
2103 ms
index.js
1912 ms
slick.min.js
1924 ms
exad-script.min.js
2109 ms
sourcebuster.min.js
2083 ms
order-attribution.min.js
2075 ms
masonry.min.js
1846 ms
main.js
2026 ms
astra-addon-65d735b4dbc686-78308013.js
1946 ms
general.min.js
1980 ms
jquery.smartmenus.min.js
2076 ms
imagesloaded.min.js
2075 ms
webpack-pro.runtime.min.js
1977 ms
webpack.runtime.min.js
2093 ms
frontend-modules.min.js
2011 ms
wp-polyfill-inert.min.js
1967 ms
regenerator-runtime.min.js
2033 ms
wp-polyfill.min.js
2082 ms
hooks.min.js
1743 ms
i18n.min.js
2071 ms
frontend.min.js
1986 ms
waypoints.min.js
1917 ms
core.min.js
1908 ms
frontend.min.js
2011 ms
elements-handlers.min.js
1967 ms
jquery.sticky.min.js
1988 ms
fbevents.js
167 ms
65910a760d62d7098ffc3c3e5.js
266 ms
jquery.zoom.min.js
1932 ms
164 ms
insight.min.js
62 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
70 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
93 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
117 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
121 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
119 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
118 ms
jquery.flexslider.min.js
1822 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xw.ttf
116 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf
145 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xw.ttf
145 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv58a-xw.ttf
144 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf
143 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
143 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
144 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
170 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
169 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
170 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
169 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
165 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
166 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
169 ms
photoswipe.min.js
1869 ms
photoswipe-ui-default.min.js
1953 ms
insight.beta.min.js
4 ms
insight_tag_errors.gif
185 ms
80 ms
underscore.min.js
1908 ms
wp-util.min.js
1940 ms
add-to-cart-variation.min.js
1940 ms
single-product.min.js
1845 ms
eicons.woff
2078 ms
fa-solid-900.woff
2146 ms
fa-regular-400.woff
1955 ms
fa-brands-400.woff
2114 ms
wtf_dino_powered_long-1.png
1971 ms
email-logo-1024x213.png
2081 ms
WTF-App-graphic-1024x793.png
2366 ms
MIS21_FINALIST-FOOD-AND-DRINK_SOCIAL-1-1-1024x538-1.jpeg
2231 ms
collectedforms.js
55 ms
banner.js
124 ms
5139711.js
104 ms
conversations-embed.js
41 ms
fb.js
46 ms
Capital_Scotland.png
2119 ms
230x0w-3-q76njqj9o37spj0fpp714nahe1mpey2gcnobv05nk0.png
2021 ms
230x0w-q76nnd6u226njbqniro698bjylqq4vh56mctkgrxj4.png
2087 ms
square-Logo-25-q76nnkpjkqgy47fqaux6t6f8popnugazvnkpeogs5c.jpg
2096 ms
wtf-dino-white-long-1024x214.png
2354 ms
b3-trans-q76nmvbwiu8e3tcma6sxkf5p4x8ne4p6qh1b0oxuf0.png
2138 ms
homepage-background-tiled-screens-top.jpg
2609 ms
STV-News-What-The-Fork.jpeg
2149 ms
homepage-background-tiled-screens-bottom.jpg
2527 ms
Right-corner-gradients-2.png
2258 ms
default-skin.png
2311 ms
woocommerce-smallscreen.min.css
345 ms
whatthefork.co.uk accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
whatthefork.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
whatthefork.co.uk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatthefork.co.uk 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 Whatthefork.co.uk 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.
whatthefork.co.uk
Open Graph data is detected on the main page of What The Fork. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: