Tools & Wizards About Us
lighthouseftc.org screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

lighthouseftc.org

Lighthouse Sober Living

Page Load Speed

2.6 sec in total

First Response

140 ms

Resources Loaded

1.9 sec

Page Rendered

533 ms

lighthouseftc.org screenshot

About Website

Click here to check amazing Lighthouse Ftc content. Otherwise, check out these important facts you probably never knew about lighthouseftc.org

The Lighthouse is a faith based sober living house.

Visit lighthouseftc.org

Key Findings

We analyzed Lighthouseftc.org page load time and found that the first response time was 140 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

lighthouseftc.org performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

lighthouseftc.org

140 ms

lighthouseftc.org

226 ms

xr_fonts.css

58 ms

highslide.css

113 ms

highslide.js

208 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that all of those requests were addressed to Lighthouseftc.org and no external sources were called. The less responsive or slowest element that took the longest time to load (426 ms) belongs to the original domain Lighthouseftc.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 247.7 kB (18%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lighthouseftc.org main page is 1.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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 70.8 kB

  • Original 82.8 kB
  • After minification 81.3 kB
  • After compression 12.0 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 70.8 kB or 86% of the original size.

Image Optimization

-14%

Potential reduce by 172.5 kB

  • Original 1.2 MB
  • After minification 1.0 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. Obviously, Lighthouse Ftc needs image optimization as it can save up to 172.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 2.0 kB

  • Original 79.1 kB
  • After minification 79.1 kB
  • After compression 77.1 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.

CSS Optimization

-9%

Potential reduce by 2.4 kB

  • Original 27.1 kB
  • After minification 27.1 kB
  • After compression 24.7 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. Lighthouseftc.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (16%)

Requests Now

120

After Optimization

101

  • Images
  • JavaScript
  • CSS

The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lighthouse Ftc. 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 from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lighthouseftc.org

lighthouseftc.org

140 ms

lighthouseftc.org

lighthouseftc.org

226 ms

xr_fonts.css

xr_fonts.css

58 ms

highslide.css

highslide.css

113 ms

highslide.js

highslide.js

208 ms

xr_main.css

xr_main.css

166 ms

custom_styles.css

custom_styles.css

168 ms

xr_text.css

xr_text.css

164 ms

roe.js

roe.js

222 ms

replaceMobileFonts.js

replaceMobileFonts.js

167 ms

prs4.js

prs4.js

225 ms

xr_all.css

xr_all.css

227 ms

jquery.js

jquery.js

280 ms

ani.css

ani.css

229 ms

52171.png

52171.png

99 ms

60587.png

60587.png

100 ms

99280.jpg

99280.jpg

101 ms

58891.jpg

58891.jpg

117 ms

39028.jpg

39028.jpg

116 ms

39029.jpg

39029.jpg

117 ms

42805.jpg

42805.jpg

209 ms

39031.jpg

39031.jpg

160 ms

39032.jpg

39032.jpg

118 ms

39033.jpg

39033.jpg

165 ms

42806.jpg

42806.jpg

214 ms

99290.jpg

99290.jpg

266 ms

99291.png

99291.png

178 ms

99292.png

99292.png

211 ms

99293.jpg

99293.jpg

218 ms

99294.jpg

99294.jpg

231 ms

40976.jpg

40976.jpg

261 ms

92552.jpg

92552.jpg

268 ms

99297.jpg

99297.jpg

317 ms

99299.png

99299.png

270 ms

99300.png

99300.png

284 ms

99301.png

99301.png

316 ms

99302.png

99302.png

319 ms

99324.png

99324.png

317 ms

99303.png

99303.png

331 ms

99325.png

99325.png

338 ms

99304.png

99304.png

370 ms

99326.png

99326.png

372 ms

99305.png

99305.png

370 ms

99327.png

99327.png

372 ms

99306.png

99306.png

384 ms

99307.png

99307.png

389 ms

99308.jpg

99308.jpg

424 ms

60494.jpg

60494.jpg

425 ms

94088.png

94088.png

426 ms

60532.png

60532.png

403 ms

92592.jpg

92592.jpg

342 ms

99337.jpg

99337.jpg

401 ms

99338.png

99338.png

367 ms

XaraWDGeneratedHTMLfont6.woff

XaraWDGeneratedHTMLfont6.woff

369 ms

XaraWDGeneratedHTMLfont8.woff

XaraWDGeneratedHTMLfont8.woff

422 ms

XaraWDGeneratedHTMLfont7.woff

XaraWDGeneratedHTMLfont7.woff

383 ms

XaraWDGeneratedHTMLfont9.woff

XaraWDGeneratedHTMLfont9.woff

383 ms

XaraWDGeneratedHTMLfont10.woff

XaraWDGeneratedHTMLfont10.woff

382 ms

XaraWDGeneratedHTMLfont11.woff

XaraWDGeneratedHTMLfont11.woff

373 ms

XaraWDGeneratedHTMLfont12.woff

XaraWDGeneratedHTMLfont12.woff

383 ms

99339.png

99339.png

354 ms

39117.jpg

39117.jpg

349 ms

39118.jpg

39118.jpg

380 ms

42832.jpg

42832.jpg

374 ms

39120.jpg

39120.jpg

360 ms

39121.jpg

39121.jpg

332 ms

39122.jpg

39122.jpg

337 ms

99346.jpg

99346.jpg

334 ms

99347.jpg

99347.jpg

373 ms

99348.jpg

99348.jpg

361 ms

92607.jpg

92607.jpg

329 ms

92608.jpg

92608.jpg

328 ms

92609.jpg

92609.jpg

334 ms

99352.jpg

99352.jpg

336 ms

92611.jpg

92611.jpg

366 ms

99354.png

99354.png

360 ms

99355.jpg

99355.jpg

327 ms

60537.png

60537.png

328 ms

60534.png

60534.png

332 ms

60536.png

60536.png

334 ms

99359.png

99359.png

364 ms

99360.png

99360.png

361 ms

99361.png

99361.png

325 ms

99365.png

99365.png

326 ms

99366.png

99366.png

328 ms

99367.png

99367.png

330 ms

99368.png

99368.png

370 ms

99369.png

99369.png

326 ms

99370.png

99370.png

323 ms

99372.png

99372.png

308 ms

101255.png

101255.png

310 ms

101256.png

101256.png

309 ms

99375.png

99375.png

323 ms

64153.png

64153.png

322 ms

64196.png

64196.png

306 ms

64154.png

64154.png

300 ms

64197.png

64197.png

301 ms

64155.png

64155.png

303 ms

64198.png

64198.png

324 ms

64156.png

64156.png

324 ms

64199.png

64199.png

322 ms

64157.png

64157.png

324 ms

64200.png

64200.png

318 ms

50446.png

50446.png

315 ms

50454.png

50454.png

327 ms

50447.png

50447.png

325 ms

50455.png

50455.png

323 ms

43133.png

43133.png

326 ms

43206.png

43206.png

319 ms

42901.png

42901.png

316 ms

42965.png

42965.png

326 ms

42902.png

42902.png

324 ms

42966.png

42966.png

327 ms

42903.png

42903.png

325 ms

42967.png

42967.png

320 ms

43199.png

43199.png

317 ms

42968.png

42968.png

327 ms

48506.png

48506.png

327 ms

48570.png

48570.png

325 ms

48514.png

48514.png

325 ms

48575.png

48575.png

324 ms

48515.png

48515.png

323 ms

48576.png

48576.png

326 ms

48516.png

48516.png

326 ms

48577.png

48577.png

325 ms

48564.png

48564.png

326 ms

48579.png

48579.png

326 ms

custom.png

custom.png

56 ms

zoomout.cur

zoomout.cur

55 ms

loader.white.gif

loader.white.gif

56 ms

Accessibility Review

lighthouseftc.org accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

lighthouseftc.org 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

SEO Factors

lighthouseftc.org SEO score

90

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 Lighthouseftc.org 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 Lighthouseftc.org 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

lighthouseftc.org

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