Tools & Wizards About Us
sarahlouise.com screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

sarahlouise.com

Welcome to Sarah Louise's Shop66

Page Load Speed

1.1 sec in total

First Response

84 ms

Resources Loaded

784 ms

Page Rendered

244 ms

sarahlouise.com screenshot

About Website

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

This is the home of sarahlouise.com

Visit sarahlouise.com

Key Findings

We analyzed Sarahlouise.com page load time and found that the first response time was 84 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

sarahlouise.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value5,210 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.5 s

1/100

10%

Network Requests Diagram

sarahlouise.com

84 ms

sarah-kelly-9200665

347 ms

blank.asp

20 ms

gtm.js

100 ms

10034870-10034150.js

50 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Sarahlouise.com, 72% (36 requests) were made to Cdn-obituaries.dignitymemorial.com and 10% (5 requests) were made to Cdn.dignitymemorial.com. The less responsive or slowest element that took the longest time to load (347 ms) relates to the external source Dignitymemorial.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.3 kB (32%)

Content Size

285.0 kB

After Optimization

194.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Sarahlouise.com main page is 285.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 162.5 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 532 B

  • Original 978 B
  • After minification 925 B
  • After compression 446 B

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 532 B or 54% of the original size.

Image Optimization

-1%

Potential reduce by 2.2 kB

  • Original 162.5 kB
  • After minification 160.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. Sarah Louise images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 87.6 kB

  • Original 121.5 kB
  • After minification 121.5 kB
  • After compression 33.8 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 87.6 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (83%)

Requests Now

42

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sarahlouise.com

sarahlouise.com

84 ms

sarah-kelly-9200665

sarah-kelly-9200665

347 ms

blank.asp

blank.asp

20 ms

gtm.js

gtm.js

100 ms

10034870-10034150.js

10034870-10034150.js

50 ms

new-reclic-browser-agent.prod.js

new-reclic-browser-agent.prod.js

73 ms

a712edbee4df77dc.css

a712edbee4df77dc.css

116 ms

321dfe9f4946877a.css

321dfe9f4946877a.css

129 ms

polyfills-0d1b80a048d4787e.js

polyfills-0d1b80a048d4787e.js

165 ms

webpack-8c7d42fc01392a0d.js

webpack-8c7d42fc01392a0d.js

195 ms

defaultVendors~main~index.js~v.1.8.18-07193b0494edee75.js

defaultVendors~main~index.js~v.1.8.18-07193b0494edee75.js

163 ms

defaultVendors~main~router.js~v.1.8.18-efa292ee37d1ac2a.js

defaultVendors~main~router.js~v.1.8.18-efa292ee37d1ac2a.js

164 ms

defaultVendors~main~react-dom.production.min.js~v.1.8.18-eb6a4031b4b239a8.js

defaultVendors~main~react-dom.production.min.js~v.1.8.18-eb6a4031b4b239a8.js

254 ms

main-cafb20c8c379a1ca.js

main-cafb20c8c379a1ca.js

252 ms

_app~__DynamicConstants.js~v.1.8.18-8d2583ae8c53ab4c.js

_app~__DynamicConstants.js~v.1.8.18-8d2583ae8c53ab4c.js

254 ms

_app~i18next.js~v.1.8.18-c487caadc58fc14b.js

_app~i18next.js~v.1.8.18-c487caadc58fc14b.js

295 ms

_app~DynamicProto.js~v.1.8.18-01c11516e2b5942f.js

_app~DynamicProto.js~v.1.8.18-01c11516e2b5942f.js

297 ms

_app~AISku.js~v.1.8.18-a53caad4d889582f.js

_app~AISku.js~v.1.8.18-a53caad4d889582f.js

298 ms

_app~ajax.js~v.1.8.18-2841f2992f67bf48.js

_app~ajax.js~v.1.8.18-2841f2992f67bf48.js

299 ms

_app~ProcessTelemetryContext.js~v.1.8.18-2be9e2b11a2a9237.js

_app~ProcessTelemetryContext.js~v.1.8.18-2be9e2b11a2a9237.js

301 ms

_app~EventHelpers.js~v.1.8.18-60191cd3d01b7812.js

_app~EventHelpers.js~v.1.8.18-60191cd3d01b7812.js

301 ms

_app~AppInsightsCore.js~v.1.8.18-4417d9174363e0f5.js

_app~AppInsightsCore.js~v.1.8.18-4417d9174363e0f5.js

302 ms

_app~Exception.js~v.1.8.18-8427b141850c41fb.js

_app~Exception.js~v.1.8.18-8427b141850c41fb.js

299 ms

_app~Sender.js~v.1.8.18-773fd2c529204df1.js

_app~Sender.js~v.1.8.18-773fd2c529204df1.js

303 ms

_app~AnalyticsPlugin.js~v.1.8.18-0d26a8540dacc732.js

_app~AnalyticsPlugin.js~v.1.8.18-0d26a8540dacc732.js

301 ms

_app-1f5b22ca2d65313e.js

_app-1f5b22ca2d65313e.js

305 ms

share~styled-components.browser.esm.js~v.1.8.18-0ef2f13ade858801.js

share~styled-components.browser.esm.js~v.1.8.18-0ef2f13ade858801.js

312 ms

index~image.js~v.1.8.18-15312b3155500a31.js

index~image.js~v.1.8.18-15312b3155500a31.js

310 ms

index~index.js~v.1.8.18-8b68cf41c4ee5d0e.js

index~index.js~v.1.8.18-8b68cf41c4ee5d0e.js

311 ms

index~redux-toolkit.esm.js~v.1.8.18-8a7f425f4f8020f8.js

index~redux-toolkit.esm.js~v.1.8.18-8a7f425f4f8020f8.js

315 ms

index~intersection-observer.js~v.1.8.18-67ef815d3c5eb40f.js

index~intersection-observer.js~v.1.8.18-67ef815d3c5eb40f.js

327 ms

index~redux.js~v.1.8.18-4ce155f07060955f.js

index~redux.js~v.1.8.18-4ce155f07060955f.js

317 ms

share~internalApiService.js~v.1.8.18-4dc212a858f30c93.js

share~internalApiService.js~v.1.8.18-4dc212a858f30c93.js

316 ms

index~cdnApiService.js~v.1.8.18-a5f46f0be3bd8510.js

index~cdnApiService.js~v.1.8.18-a5f46f0be3bd8510.js

315 ms

index~FooterNeptuneSociety.jsx~v.1.8.18-f8c5263edbd59936.js

index~FooterNeptuneSociety.jsx~v.1.8.18-f8c5263edbd59936.js

316 ms

index~Services.jsx~v.1.8.18-02ce58c17a62a4ba.js

index~Services.jsx~v.1.8.18-02ce58c17a62a4ba.js

317 ms

index~ObituaryDetails.jsx~v.1.8.18-0fb1d0bd394bf64d.js

index~ObituaryDetails.jsx~v.1.8.18-0fb1d0bd394bf64d.js

325 ms

index~FooterTridentSociety.jsx~v.1.8.18-6e2a63070ae7267e.js

index~FooterTridentSociety.jsx~v.1.8.18-6e2a63070ae7267e.js

317 ms

%5B...obituaryData%5D-5e2895badd952e6e.js

%5B...obituaryData%5D-5e2895badd952e6e.js

318 ms

_buildManifest.js

_buildManifest.js

324 ms

_ssgManifest.js

_ssgManifest.js

323 ms

dm_water.jpg

dm_water.jpg

48 ms

sarah-kelly-calgary-ab-obituary.jpg

sarah-kelly-calgary-ab-obituary.jpg

242 ms

36245-source

36245-source

39 ms

38799-source

38799-source

63 ms

Lato-Regular.woff

Lato-Regular.woff

139 ms

Lato-Black.woff

Lato-Black.woff

22 ms

MrsEaves-Italic.woff

MrsEaves-Italic.woff

25 ms

Lato-Bold.woff

Lato-Bold.woff

39 ms

MrsEavesOT-Roman.woff

MrsEavesOT-Roman.woff

38 ms

Accessibility Review

sarahlouise.com accessibility score

68

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

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

sarahlouise.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sarahlouise.com 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 Sarahlouise.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

sarahlouise.com

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