Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

lilycreeklodge.com

Lily Creek Lodge Dahlonega Georgia Welcome to the North Georgia

Page Load Speed

3.9 sec in total

First Response

111 ms

Resources Loaded

3.8 sec

Page Rendered

55 ms

lilycreeklodge.com screenshot

About Website

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

Welcome to Lily Creek Lodge located in Dahlonega Georgia. We are just one hour north of Atlanta and conveniently located to visit the Historic Town Of Dahlonega, Local Waterfalls and Wineries and the ...

Visit lilycreeklodge.com

Key Findings

We analyzed Lilycreeklodge.com page load time and found that the first response time was 111 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

lilycreeklodge.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.67

8/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

www.lilycreeklodge.com

111 ms

minified.js

46 ms

focus-within-polyfill.js

45 ms

polyfill.min.js

45 ms

thunderbolt-commons.5df16dfe.bundle.min.js

183 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lilycreeklodge.com, 75% (89 requests) were made to Static.wixstatic.com and 12% (14 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 700.9 kB (42%)

Content Size

1.7 MB

After Optimization

972.8 kB

In fact, the total size of Lilycreeklodge.com main page is 1.7 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. 40% of websites need less resources to load. HTML takes 872.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 697.3 kB

  • Original 872.0 kB
  • After minification 870.2 kB
  • After compression 174.7 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 697.3 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 557.3 kB
  • After minification 557.3 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. Lily Creek Lodge images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 244.3 kB
  • After minification 244.3 kB
  • After compression 240.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 10 (10%)

Requests Now

104

After Optimization

94

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

Accessibility Review

lilycreeklodge.com accessibility score

92

Accessibility Issues

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

High

ARIA IDs are not unique

Best Practices

lilycreeklodge.com 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

lilycreeklodge.com SEO score

100

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

Open Graph data is detected on the main page of Lily Creek Lodge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: