803 ms in total
85 ms
619 ms
99 ms
Click here to check amazing Lyttle content. Otherwise, check out these important facts you probably never knew about lyttle.co
Scott Lyttle is a Sydney-based Web Designer and Developer collaborating with passionate people around the world to bring fresh and creative ideas to the web.
Visit lyttle.coWe analyzed Lyttle.co page load time and found that the first response time was 85 ms and then it took 718 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
lyttle.co performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value3.5 s
64/100
25%
Value2.5 s
98/100
10%
Value30 ms
100/100
30%
Value0.069
96/100
15%
Value2.5 s
98/100
10%
85 ms
143 ms
63 ms
223 ms
77 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Lyttle.co, 74% (17 requests) were made to Scottlyttle.com and 9% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (223 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 210.8 kB (5%)
4.0 MB
3.8 MB
In fact, the total size of Lyttle.co main page is 4.0 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. 55% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 12.9 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 12.9 kB or 76% of the original size.
Potential reduce by 164.1 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. Lyttle images are well optimized though.
Potential reduce by 33.9 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 33.9 kB or 38% of the original size.
Number of requests can be reduced by 4 (19%)
21
17
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lyttle. 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 JavaScripts and as a result speed up the page load time.
lyttle.co
85 ms
scottlyttle.com
143 ms
modernizr.min.js
63 ms
yae8cov.js
223 ms
jquery.min.js
77 ms
waitforimages.min.js
61 ms
nicholson.jpg
68 ms
analytics.js
36 ms
ambush.jpg
26 ms
scaf.jpg
30 ms
creatingonline.png
55 ms
gayby.jpg
57 ms
formist.jpg
46 ms
vossy.jpg
57 ms
ycbs.jpg
54 ms
ausvintage.jpg
58 ms
workshop.jpg
51 ms
leilajeffreys2.jpg
83 ms
ringstudio.jpg
81 ms
biancachang2.jpg
59 ms
365.jpg
78 ms
scottlyttle.com
89 ms
collect
23 ms
lyttle.co 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.
lyttle.co 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lyttle.co SEO score
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 Lyttle.co 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 Lyttle.co 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.
lyttle.co
Open Graph description is not detected on the main page of Lyttle. 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: