11.4 sec in total
1.6 sec
9.2 sec
599 ms
Welcome to fattycrabs.com homepage info - get ready to check Fattycrabs best content right away, or after learning these important things about fattycrabs.com
| Eat Drink KL PJ Klang Valley Malaysia | Online Seafood Restaurant Table Reservation | www.FattyCrabs.com Fresh Seafood Restaurant At Taman Seputeh | Malaysia Fresh Crab And Seafood & Restaurant | ...
Visit fattycrabs.comWe analyzed Fattycrabs.com page load time and found that the first response time was 1.6 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fattycrabs.com performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value10.9 s
0/100
25%
Value23.7 s
0/100
10%
Value33,580 ms
0/100
30%
Value0.012
100/100
15%
Value58.7 s
0/100
10%
1635 ms
20 ms
251 ms
142 ms
144 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 86% of them (85 requests) were addressed to the original Fattycrabs.com, 8% (8 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Fattycrabs.com.
Page size can be reduced by 1.4 MB (15%)
9.4 MB
8.0 MB
In fact, the total size of Fattycrabs.com main page is 9.4 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. 70% of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.
Potential reduce by 87.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 19.4 kB, which is 19% 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 87.4 kB or 88% of the original size.
Potential reduce by 501.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. Fattycrabs images are well optimized though.
Potential reduce by 329.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 329.4 kB or 70% of the original size.
Potential reduce by 475.5 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. Fattycrabs.com needs all CSS files to be minified and compressed as it can save up to 475.5 kB or 82% of the original size.
Number of requests can be reduced by 43 (52%)
82
39
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fattycrabs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.fattycrabs.com
1635 ms
fbevents.js
20 ms
jquery.js
251 ms
jquery-migrate.min.js
142 ms
avia-compat.js
144 ms
layerslider.kreaturamedia.jquery.js
222 ms
greensock.js
218 ms
layerslider.transitions.js
148 ms
normalize.css
217 ms
style.css
353 ms
prettyPhoto.css
242 ms
grid.css
368 ms
custom.css
364 ms
grid.css
368 ms
base.css
365 ms
layout.css
387 ms
shortcodes.css
424 ms
magnific-popup.css
416 ms
mediaelementplayer.css
412 ms
enfold.css
451 ms
layerslider.css
416 ms
css
44 ms
css
52 ms
css
62 ms
jquery.fancybox.css
1660 ms
30 ms
jquery.mousewheel-3.0.6.pack.js
1892 ms
jquery.fancybox.pack.js
2323 ms
style.css
448 ms
dashicons.min.css
511 ms
jquery.form.min.js
470 ms
scripts.js
519 ms
avia.js
624 ms
shortcodes.js
648 ms
jquery.magnific-popup.min.js
597 ms
mediaelement-and-player.min.js
732 ms
wp-mediaelement.js
698 ms
comment-reply.min.js
722 ms
testimonial.js
788 ms
jquery.easing.js
821 ms
jquery.touchwipe.js
800 ms
cleantalk_nocache.js
849 ms
css
86 ms
menu-icon.png
1421 ms
search-submit.png
94 ms
logo.png
179 ms
line-right.png
147 ms
shine.png
931 ms
carousel.gif
217 ms
button-prev.png
252 ms
corols9.png
680 ms
slider.png
323 ms
title.png
394 ms
button.png
411 ms
corols1.png
932 ms
corols21.png
929 ms
corols5.png
930 ms
corols7.png
1177 ms
corols31.png
932 ms
button-next.png
928 ms
banner.png
1520 ms
trip.png
966 ms
newimage.png
1610 ms
b1.jpg
1081 ms
b2.jpg
1119 ms
b3.png
1506 ms
sli1.png
1520 ms
img1lar.jpg
1384 ms
img3lar.jpg
1586 ms
newcrablarge.jpg
2059 ms
Claypot-Crab-Rice.png
1593 ms
fatty-crab_07.png
1610 ms
fatty-crab_09.png
1593 ms
fatty-crab_12.png
1718 ms
00000000000000000000000000000000
1677 ms
ajax-loader.gif
3137 ms
search.png
1637 ms
MVabO2jbLZ8M0pzO6jqg2fesZW2xOQ-xsNqO47m55DA.ttf
35 ms
DG8mXG-5TR8cZWqlGcHP5HYhjbSpvc47ee6xR_80Hnw.ttf
86 ms
fMdPRPskyY3ckg8ymVQ5NiwlidHJgAgmTjOEEzwu1L8.ttf
102 ms
em1T6bxBT1C9Ui5lcPwYdywlidHJgAgmTjOEEzwu1L8.ttf
118 ms
kA7V7gLI3uMMlXWrnQ_35SwlidHJgAgmTjOEEzwu1L8.ttf
119 ms
kcO_Mk7pjy8jlu86STaVzywlidHJgAgmTjOEEzwu1L8.ttf
119 ms
H8N28OeR1G4cL0Fdzv8eVCZ2oysoEQEeKwjgmXLRnTc.ttf
33 ms
title-bg.png
1601 ms
blackfat_demo-webfont.woff
1609 ms
do.png
1606 ms
dot.png
1550 ms
line.png
1656 ms
title-tail.png
1641 ms
fatty-crab_18.png
1585 ms
fatty-crab_30.png
1516 ms
nav.png
4038 ms
sprite-social.png
1252 ms
tick.png
1220 ms
lXoKq2PC8Z_S1wl-BwvrB-vvDin1pK8aKteLpeZ5c0A.ttf
24 ms
skin.css
3124 ms
admin-ajax.php
2783 ms
print.css
70 ms
fattycrabs.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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.
fattycrabs.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fattycrabs.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Fattycrabs.com 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 Fattycrabs.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.
fattycrabs.com
Open Graph description is not detected on the main page of Fattycrabs. 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: