5.1 sec in total
434 ms
4.2 sec
492 ms
Welcome to cuttlefish.com homepage info - get ready to check Cuttlefish best content right away, or after learning these important things about cuttlefish.com
Cuttlefish is a web, app and design company based in Loughborough. We build content managed websites, mobile apps, and offer digital design and print services.
Visit cuttlefish.comWe analyzed Cuttlefish.com page load time and found that the first response time was 434 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cuttlefish.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value8.0 s
2/100
25%
Value6.2 s
43/100
10%
Value570 ms
52/100
30%
Value0.419
23/100
15%
Value6.4 s
60/100
10%
434 ms
390 ms
18 ms
307 ms
336 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 92% of them (55 requests) were addressed to the original Cuttlefish.com, 5% (3 requests) were made to Fast.fonts.net and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Cuttlefish.com.
Page size can be reduced by 71.9 kB (48%)
150.4 kB
78.5 kB
In fact, the total size of Cuttlefish.com main page is 150.4 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. 30% of websites need less resources to load. Javascripts take 83.0 kB which makes up the majority of the site volume.
Potential reduce by 58.2 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 16.2 kB, which is 24% 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 58.2 kB or 86% of the original size.
Potential reduce by 13.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 13.7 kB or 16% of the original size.
Number of requests can be reduced by 25 (44%)
57
32
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cuttlefish. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
cuttlefish.com
434 ms
stylesheet148.css
390 ms
jquery.min.js
18 ms
jquery.cf.min.js
307 ms
portfolio.js
336 ms
communityportals.js
362 ms
slick.min.js
364 ms
quotes.js
341 ms
jquery.flexslider.js
642 ms
jquery.cportals.js
599 ms
email-decode.min.js
350 ms
default-content.css
144 ms
default-controlpanel.css
304 ms
default-forms.css
378 ms
default-layout.css
305 ms
default-reset.css
448 ms
default-survey.css
526 ms
default-tiles.css
566 ms
default-cookies.css
620 ms
a5912c67-ea8c-4b13-9dbb-0fdadc4edf10.css
88 ms
cf-logo-white.svg
260 ms
hero-wave-top.svg
262 ms
hero-wave-bottom.svg
262 ms
800x.png
647 ms
800x.png
715 ms
800x.png
569 ms
section-wave.svg
518 ms
william-the-worm.svg
515 ms
original.svg
623 ms
original.svg
853 ms
original.svg
909 ms
original.svg
1062 ms
original.svg
959 ms
original.svg
972 ms
original.svg
1032 ms
original.svg
1163 ms
original.svg
1239 ms
original.svg
1294 ms
original.svg
1290 ms
original.svg
1352 ms
original.svg
1395 ms
original.svg
1478 ms
original.svg
1557 ms
original.svg
1622 ms
original.svg
1705 ms
original.svg
1658 ms
text-about-us.svg
1660 ms
original.svg
1796 ms
text-quote.svg
1803 ms
large.png
2024 ms
large.png
1988 ms
large.png
2078 ms
cf-logo-basic.svg
1800 ms
social-instagram.svg
2053 ms
social-facebook.svg
2055 ms
social-twitter.svg
2037 ms
aa19e7c7-176b-4241-b77b-aeab4fa42f7e.woff
96 ms
0610e07b-93ea-4f1f-b469-1a2a02398b58.woff
120 ms
print.css
276 ms
gtm.js
54 ms
cuttlefish.com 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.
cuttlefish.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
cuttlefish.com 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
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 Cuttlefish.com 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 Cuttlefish.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.
cuttlefish.com
Open Graph data is detected on the main page of Cuttlefish. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: