Tools & Wizards About Us
flintofts.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% 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

  • 98

    SEO

    Google-friendlier than
    92% of websites

flintofts.com

Page Load Speed

227 ms in total

First Response

32 ms

Resources Loaded

195 ms

Page Rendered

0 ms

flintofts.com screenshot

About Website

Visit flintofts.com now to see the best up-to-date Flintofts content for United States and also check out these interesting facts you probably never knew about flintofts.com

Flintoft's Funeral Home & Crematory, Located in Issaquah, WA. Highly Trained, Caring Professionals Here To Serve You In Your Time Of Need.

Visit flintofts.com

Key Findings

We analyzed Flintofts.com page load time and found that the first response time was 32 ms and then it took 195 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

flintofts.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.367

29/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

flintofts.com

32 ms

www.flintofts.com

11 ms

www.flintofts.com

46 ms

gtm.js

61 ms

gtm.js

98 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 22% of them (4 requests) were addressed to the original Flintofts.com, 39% (7 requests) were made to D2zeeo94hsmapq.cloudfront.net and 22% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (98 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 223.2 kB (58%)

Content Size

384.1 kB

After Optimization

160.9 kB

  • HTML
  • JavaScript

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

HTML Optimization

-77%

Potential reduce by 223.0 kB

  • Original 287.9 kB
  • After minification 286.4 kB
  • After compression 64.9 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 223.0 kB or 77% of the original size.

JavaScript Optimization

-0%

Potential reduce by 233 B

  • Original 96.2 kB
  • After minification 96.2 kB
  • After compression 96.0 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 13 (87%)

Requests Now

15

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

flintofts.com

flintofts.com

32 ms

www.flintofts.com

www.flintofts.com

11 ms

www.flintofts.com

www.flintofts.com

46 ms

gtm.js

gtm.js

61 ms

gtm.js

gtm.js

98 ms

vue.min.js

vue.min.js

46 ms

vuex.min.js

vuex.min.js

76 ms

chunk-store.8e42d9ef.js

chunk-store.8e42d9ef.js

36 ms

chunk-app.0ff5f1ad.js

chunk-app.0ff5f1ad.js

38 ms

chunk-windows-size.fc7b6a05.js

chunk-windows-size.fc7b6a05.js

40 ms

chunk-init-data.73bd3877.js

chunk-init-data.73bd3877.js

40 ms

chunk-generate-css.9984f9fc.js

chunk-generate-css.9984f9fc.js

41 ms

chunk-vendors.d07f823b.js

chunk-vendors.d07f823b.js

41 ms

app.c40b6e24.js

app.c40b6e24.js

41 ms

gtm.js

gtm.js

92 ms

css

css

49 ms

js

js

66 ms

GetAntiforgeryToken.js

GetAntiforgeryToken.js

14 ms

Accessibility Review

flintofts.com accessibility score

96

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

SEO Factors

flintofts.com SEO score

98

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flintofts.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Flintofts.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

flintofts.com

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