Tools & Wizards About Us
paululee.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

paululee.com

Home | Clayton Funeral Home and Cemetery Services located in Pearla...

Page Load Speed

1.2 sec in total

First Response

158 ms

Resources Loaded

893 ms

Page Rendered

158 ms

paululee.com screenshot

About Website

Welcome to paululee.com homepage info - get ready to check Paululee best content for United States right away, or after learning these important things about paululee.com

John G. Clayton is a third-generation funeral professional well versed in the traditions of all faiths, ethnic backgrounds, and military funerals. W

Visit paululee.com

Key Findings

We analyzed Paululee.com page load time and found that the first response time was 158 ms and then it took 1.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

paululee.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.349

32/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

www.paululee.com

158 ms

home.cfm

63 ms

home.cfm

304 ms

jquery.min.js

97 ms

analytics.js

50 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 82% of them (28 requests) were addressed to the original Paululee.com, 12% (4 requests) were made to Google-analytics.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (304 ms) belongs to the original domain Paululee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.3 kB (48%)

Content Size

219.3 kB

After Optimization

115.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Paululee.com main page is 219.3 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. 20% of websites need less resources to load. Javascripts take 114.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 27.5 kB

  • Original 33.0 kB
  • After minification 25.0 kB
  • After compression 5.5 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. This page needs HTML code to be minified as it can gain 8.0 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 27.5 kB or 83% of the original size.

Image Optimization

-23%

Potential reduce by 16.3 kB

  • Original 71.5 kB
  • After minification 55.2 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. Obviously, Paululee needs image optimization as it can save up to 16.3 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 60.6 kB

  • Original 114.9 kB
  • After minification 114.9 kB
  • After compression 54.3 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 60.6 kB or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (23%)

Requests Now

30

After Optimization

23

  • Images
  • JavaScript

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

Network Requests Diagram

www.paululee.com

www.paululee.com

158 ms

home.cfm

home.cfm

63 ms

home.cfm

home.cfm

304 ms

jquery.min.js

jquery.min.js

97 ms

analytics.js

analytics.js

50 ms

gtm.js

gtm.js

49 ms

bg.gif

bg.gif

42 ms

top_bg.gif

top_bg.gif

42 ms

spacer.gif

spacer.gif

47 ms

left_corner.jpg

left_corner.jpg

46 ms

13374_banner.png

13374_banner.png

46 ms

topbar_curve.gif

topbar_curve.gif

46 ms

visa.gif

visa.gif

47 ms

mc.gif

mc.gif

46 ms

45_2579.JPG

45_2579.JPG

72 ms

left-col-cta-small-florist3.png

left-col-cta-small-florist3.png

72 ms

left-col-cta-small-bookstore3.png

left-col-cta-small-bookstore3.png

73 ms

up_right.gif

up_right.gif

72 ms

mailinglist.jpg

mailinglist.jpg

83 ms

3616252_small.jpg

3616252_small.jpg

72 ms

3614099_small.jpg

3614099_small.jpg

90 ms

3613250_small.jpg

3613250_small.jpg

91 ms

3613364_small.jpg

3613364_small.jpg

93 ms

3598564_small.JPG

3598564_small.JPG

91 ms

3598590_small.jpg

3598590_small.jpg

93 ms

3596714_small.jpg

3596714_small.jpg

103 ms

3596455_small.jpg

3596455_small.jpg

110 ms

3581571_small.jpg

3581571_small.jpg

112 ms

3570155_small.jpg

3570155_small.jpg

113 ms

1.gif

1.gif

113 ms

collect

collect

27 ms

collect

collect

72 ms

collect

collect

33 ms

collect

collect

8 ms

Accessibility Review

paululee.com accessibility score

62

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-*] attributes do not match their roles

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

paululee.com SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paululee.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 Paululee.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

paululee.com

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