Tools & Wizards About Us
pulliam.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

pulliam.com

Ft. Worth Pool Builder, Weatherford, pool renovation Keller

Page Load Speed

3.8 sec in total

First Response

836 ms

Resources Loaded

1.8 sec

Page Rendered

1.2 sec

pulliam.com screenshot

About Website

Welcome to pulliam.com homepage info - get ready to check Pulliam best content right away, or after learning these important things about pulliam.com

Pulliam Pools is a Ft. Worth pool builder specializing in custom pool design, new pool construction, pool renovation & more for Weatherford, Keller & more.

Visit pulliam.com

Key Findings

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

Performance Metrics

pulliam.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value24.1 s

0/100

10%

TBT (Total Blocking Time)

Value46,090 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.267

46/100

15%

TTI (Time to Interactive)

Value69.9 s

0/100

10%

Network Requests Diagram

www.pulliam.com

836 ms

js

119 ms

gtm.js

159 ms

gfpmoe2qat

158 ms

fbevents.js

68 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 61% of them (25 requests) were addressed to the original Pulliam.com, 10% (4 requests) were made to Maps.googleapis.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (836 ms) belongs to the original domain Pulliam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.6 kB (17%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pulliam.com main page is 1.3 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. 65% of websites need less resources to load. Images take 702.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 168.4 kB

  • Original 197.7 kB
  • After minification 172.5 kB
  • After compression 29.3 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 25.2 kB, which is 13% 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 168.4 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 54.4 kB

  • Original 702.4 kB
  • After minification 648.1 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. Pulliam images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.2 kB

  • Original 407.4 kB
  • After minification 407.4 kB
  • After compression 403.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

-6%

Potential reduce by 566 B

  • Original 9.3 kB
  • After minification 9.2 kB
  • After compression 8.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. Pulliam.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

36

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pulliam.com

www.pulliam.com

836 ms

js

js

119 ms

gtm.js

gtm.js

159 ms

gfpmoe2qat

gfpmoe2qat

158 ms

fbevents.js

fbevents.js

68 ms

sbi-styles.min.css

sbi-styles.min.css

63 ms

advanced-location-dynamics-public.css

advanced-location-dynamics-public.css

112 ms

logo.png

logo.png

179 ms

loader.js

loader.js

96 ms

loader.js

loader.js

108 ms

embed

embed

358 ms

widget.js

widget.js

105 ms

jquery.min.js

jquery.min.js

193 ms

production-dist.js

production-dist.js

329 ms

t.js

t.js

143 ms

sbi-scripts.min.js

sbi-scripts.min.js

162 ms

24-Top-50-150x136-c-center.jpg

24-Top-50-150x136-c-center.jpg

161 ms

22_6347-lupton-dr-dallas-tx-High-Res-33-640x640-c-center.jpg

22_6347-lupton-dr-dallas-tx-High-Res-33-640x640-c-center.jpg

383 ms

JimiSmithPhotographyEW10-480x300-c-center.jpg

JimiSmithPhotographyEW10-480x300-c-center.jpg

374 ms

JimiSmithPhotographyEW03-10-480x300-c-center.jpg

JimiSmithPhotographyEW03-10-480x300-c-center.jpg

377 ms

use-this-pulliam-480x300-c-center.jpg

use-this-pulliam-480x300-c-center.jpg

374 ms

Jimi-Smith-Photography01MAS-1-480x300-c-center.jpg

Jimi-Smith-Photography01MAS-1-480x300-c-center.jpg

374 ms

Jimi-Smith-Photography08MAS-1-480x300-c-center.jpg

Jimi-Smith-Photography08MAS-1-480x300-c-center.jpg

376 ms

400246541_286641140386916_3442802281006939051_nfull.jpg

400246541_286641140386916_3442802281006939051_nfull.jpg

380 ms

398472465_859047679036670_701852903527345736_nfull.jpg

398472465_859047679036670_701852903527345736_nfull.jpg

394 ms

391417339_853575616325663_6333641575084147435_nfull.jpg

391417339_853575616325663_6333641575084147435_nfull.jpg

403 ms

387267837_1053218646028406_7635976953675946220_nfull.jpg

387267837_1053218646028406_7635976953675946220_nfull.jpg

410 ms

google.jpg

google.jpg

415 ms

breeez-navy-logo.svg

breeez-navy-logo.svg

424 ms

isotope.pkgd.js

isotope.pkgd.js

57 ms

sbi-sprite.png

sbi-sprite.png

299 ms

Mont-Regular.ttf

Mont-Regular.ttf

344 ms

Mont-Book.ttf

Mont-Book.ttf

325 ms

Mont-Light.ttf

Mont-Light.ttf

316 ms

Mont-SemiBold.ttf

Mont-SemiBold.ttf

415 ms

clarity.js

clarity.js

19 ms

js

js

42 ms

geometry.js

geometry.js

3 ms

search.js

search.js

7 ms

main.js

main.js

15 ms

c.gif

c.gif

7 ms

Accessibility Review

pulliam.com accessibility score

94

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.

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

pulliam.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

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

pulliam.com

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