Tools & Wizards About Us
lillieanns.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

lillieanns.com

Massage West Loop & South Loop Chicago - Massage Therapy & Skin Care Spa

Page Load Speed

2.5 sec in total

First Response

143 ms

Resources Loaded

2 sec

Page Rendered

271 ms

lillieanns.com screenshot

About Website

Visit lillieanns.com now to see the best up-to-date Lillieanns content and also check out these interesting facts you probably never knew about lillieanns.com

LillieAnn's Massage & Skin Care is the best massage and skin care spa in the West Loop and South Loop of Chicago, IL. We offer massage therapy, skin care, facial, waxing and spa services.

Visit lillieanns.com

Key Findings

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

Performance Metrics

lillieanns.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.136

80/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

lillieanns.com

143 ms

lillieanns.com

396 ms

css

46 ms

api.js

47 ms

c8724ea1b3.js

77 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 69% of them (52 requests) were addressed to the original Lillieanns.com, 8% (6 requests) were made to Apis.google.com and 5% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (910 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 221.7 kB (20%)

Content Size

1.1 MB

After Optimization

865.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lillieanns.com main page is 1.1 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. Javascripts take 585.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 56.0 kB

  • Original 71.6 kB
  • After minification 69.4 kB
  • After compression 15.6 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 56.0 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 1.4 kB

  • Original 278.9 kB
  • After minification 277.4 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. Lillieanns images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 122.3 kB

  • Original 585.7 kB
  • After minification 585.5 kB
  • After compression 463.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 122.3 kB or 21% of the original size.

CSS Optimization

-28%

Potential reduce by 42.0 kB

  • Original 150.8 kB
  • After minification 148.4 kB
  • After compression 108.8 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. Lillieanns.com needs all CSS files to be minified and compressed as it can save up to 42.0 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (77%)

Requests Now

65

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lillieanns.com

lillieanns.com

143 ms

lillieanns.com

lillieanns.com

396 ms

css

css

46 ms

api.js

api.js

47 ms

c8724ea1b3.js

c8724ea1b3.js

77 ms

wp-customer-reviews.css

wp-customer-reviews.css

159 ms

style.min.css

style.min.css

287 ms

ssb-ui-style.css

ssb-ui-style.css

232 ms

font-awesome.css

font-awesome.css

235 ms

dashicons.min.css

dashicons.min.css

290 ms

to-top-public.css

to-top-public.css

222 ms

pagenavi-css.css

pagenavi-css.css

223 ms

bootstrap.min.css

bootstrap.min.css

351 ms

style.css

style.css

290 ms

tsumugi.css

tsumugi.css

295 ms

css

css

65 ms

font-awesome.min.css

font-awesome.min.css

300 ms

dynamic-mobmenu.css

dynamic-mobmenu.css

348 ms

css

css

66 ms

mobmenu-icons.css

mobmenu-icons.css

358 ms

mobmenu.css

mobmenu.css

352 ms

jquery.min.js

jquery.min.js

423 ms

jquery-migrate.min.js

jquery-migrate.min.js

363 ms

wp-customer-reviews.js

wp-customer-reviews.js

435 ms

ssb-ui-js.js

ssb-ui-js.js

437 ms

to-top-public.js

to-top-public.js

422 ms

mobmenu.js

mobmenu.js

436 ms

recaptcha__en.js

recaptcha__en.js

36 ms

platform.js

platform.js

99 ms

flexslider.css

flexslider.css

386 ms

public.css

public.css

439 ms

core.min.js

core.min.js

446 ms

effect.min.js

effect.min.js

474 ms

effect-shake.min.js

effect-shake.min.js

474 ms

tether.min.js

tether.min.js

479 ms

bootstrap.min.js

bootstrap.min.js

480 ms

navigation.js

navigation.js

547 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

546 ms

api.js

api.js

97 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

549 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

547 ms

wp-polyfill.min.js

wp-polyfill.min.js

573 ms

index.js

index.js

771 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

576 ms

script.min.js

script.min.js

576 ms

lazyload.min.js

lazyload.min.js

575 ms

c8724ea1b3.css

c8724ea1b3.css

80 ms

font-awesome-css.min.css

font-awesome-css.min.css

13 ms

circle01.jpg

circle01.jpg

183 ms

footer.jpg

footer.jpg

225 ms

rnCr-xNNww_2s0amA9M5kn0.ttf

rnCr-xNNww_2s0amA9M5kn0.ttf

67 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

335 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

54 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

74 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

44 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

43 ms

fastbutton

fastbutton

89 ms

fa-solid-900.woff

fa-solid-900.woff

278 ms

fa-regular-400.woff

fa-regular-400.woff

173 ms

postmessageRelay

postmessageRelay

54 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

30 ms

rpc:shindig_random.js

rpc:shindig_random.js

25 ms

developers.google.com

developers.google.com

910 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

lillieanns-logo.svg

lillieanns-logo.svg

67 ms

slide01.jpg

slide01.jpg

180 ms

slide-2.jpeg

slide-2.jpeg

238 ms

slide-3-1.jpg

slide-3-1.jpg

69 ms

slide-5.jpeg

slide-5.jpeg

208 ms

top-img.png

top-img.png

237 ms

facebook.png

facebook.png

108 ms

google-plus.png

google-plus.png

134 ms

yelp.png

yelp.png

173 ms

embed

embed

23 ms

js

js

56 ms

Accessibility Review

lillieanns.com accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

lillieanns.com best practices score

75

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lillieanns.com SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Lillieanns.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 Lillieanns.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.

Social Sharing Optimization

lillieanns.com

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