Tools & Wizards About Us
lindsayell.is screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

lindsayell.is

Lindsay Ellis

Page Load Speed

1.1 sec in total

First Response

85 ms

Resources Loaded

911 ms

Page Rendered

90 ms

lindsayell.is screenshot

About Website

Welcome to lindsayell.is homepage info - get ready to check Lindsay Ell best content right away, or after learning these important things about lindsayell.is

Visit lindsayell.is

Key Findings

We analyzed Lindsayell.is page load time and found that the first response time was 85 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

lindsayell.is performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value16.4 s

0/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

www.lindsayell.is

85 ms

css2

117 ms

legacy.js

103 ms

modern.js

119 ms

extract-css-runtime-6dfd641f22e931331024-min.en-US.js

105 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Lindsayell.is, 45% (9 requests) were made to Assets.squarespace.com and 15% (3 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (427 ms) relates to the external source Images.squarespace-cdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.9 kB (4%)

Content Size

4.4 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lindsayell.is main page is 4.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. 50% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 89.1 kB

  • Original 106.8 kB
  • After minification 97.6 kB
  • After compression 17.8 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 89.1 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 99.4 kB

  • Original 3.3 MB
  • After minification 3.2 MB

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. Lindsay Ell images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 6.3 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 1.0 MB

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.

CSS Optimization

-1%

Potential reduce by 135 B

  • Original 15.3 kB
  • After minification 15.3 kB
  • After compression 15.2 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. Lindsayell.is has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (74%)

Requests Now

19

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lindsayell.is

www.lindsayell.is

85 ms

css2

css2

117 ms

legacy.js

legacy.js

103 ms

modern.js

modern.js

119 ms

extract-css-runtime-6dfd641f22e931331024-min.en-US.js

extract-css-runtime-6dfd641f22e931331024-min.en-US.js

105 ms

extract-css-moment-js-vendor-6f117db4eb7fd4392375-min.en-US.js

extract-css-moment-js-vendor-6f117db4eb7fd4392375-min.en-US.js

264 ms

cldr-resource-pack-1edcdb1d4b6b94ec8c7e-min.en-US.js

cldr-resource-pack-1edcdb1d4b6b94ec8c7e-min.en-US.js

111 ms

common-vendors-stable-3598b219a3c023c1915a-min.en-US.js

common-vendors-stable-3598b219a3c023c1915a-min.en-US.js

133 ms

common-vendors-ad3a16dda3a9dce71609-min.en-US.js

common-vendors-ad3a16dda3a9dce71609-min.en-US.js

297 ms

common-6a9140165b0a4377fb2f-min.en-US.js

common-6a9140165b0a4377fb2f-min.en-US.js

320 ms

performance-0be2933ca4c7aa421a69-min.en-US.js

performance-0be2933ca4c7aa421a69-min.en-US.js

114 ms

site.css

site.css

136 ms

website.components.shape.styles.css

website.components.shape.styles.css

110 ms

website.components.shape.visitor.js

website.components.shape.visitor.js

109 ms

website.components.shape.handlers.js

website.components.shape.handlers.js

109 ms

static.css

static.css

104 ms

site-bundle.4df6f348a832dc61e261a099a8ca9b31.js

site-bundle.4df6f348a832dc61e261a099a8ca9b31.js

113 ms

_IMG_0534+edited.png

_IMG_0534+edited.png

254 ms

Ellis_Axiom%27s%2520End_edited.jpg

Ellis_Axiom%27s%2520End_edited.jpg

417 ms

crop.jpg

crop.jpg

427 ms

Accessibility Review

lindsayell.is accessibility score

94

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

lindsayell.is best practices score

92

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

Page has valid source maps

SEO Factors

lindsayell.is SEO score

93

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lindsayell.is 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 Lindsayell.is 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

lindsayell.is

Open Graph description is not detected on the main page of Lindsay Ell. 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: