Tools & Wizards About Us
drewpendergrass.com screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

drewpendergrass.com

Home | Drew Pendergrass

Page Load Speed

1.5 sec in total

First Response

237 ms

Resources Loaded

787 ms

Page Rendered

521 ms

drewpendergrass.com screenshot

About Website

Click here to check amazing Drew Pendergrass content. Otherwise, check out these important facts you probably never knew about drewpendergrass.com

DrewPendergrass.com is the personal website of proud website-owner Drew Pendergrass

Visit drewpendergrass.com

Key Findings

We analyzed Drewpendergrass.com page load time and found that the first response time was 237 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

drewpendergrass.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

drewpendergrass.com

237 ms

FrontTheme.css

74 ms

501ccf80-df0d-4d65-9219-1b62c76d81c2

91 ms

drewsite.png

549 ms

happy_computer.gif

124 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 59% of them (10 requests) were addressed to the original Drewpendergrass.com, 29% (5 requests) were made to Embeds.beehiiv.com and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (549 ms) belongs to the original domain Drewpendergrass.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 680.6 kB (26%)

Content Size

2.6 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Drewpendergrass.com main page is 2.6 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. 20% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 7.9 kB

  • Original 12.5 kB
  • After minification 11.1 kB
  • After compression 4.6 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 1.4 kB, which is 11% 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 7.9 kB or 63% of the original size.

Image Optimization

-28%

Potential reduce by 672.3 kB

  • Original 2.4 MB
  • After minification 1.8 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, Drew Pendergrass needs image optimization as it can save up to 672.3 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 39 B

  • Original 133.0 kB
  • After minification 133.0 kB
  • After compression 133.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.

CSS Optimization

-26%

Potential reduce by 349 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 1.0 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. Drewpendergrass.com needs all CSS files to be minified and compressed as it can save up to 349 B or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (27%)

Requests Now

15

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

drewpendergrass.com

drewpendergrass.com

237 ms

FrontTheme.css

FrontTheme.css

74 ms

501ccf80-df0d-4d65-9219-1b62c76d81c2

501ccf80-df0d-4d65-9219-1b62c76d81c2

91 ms

drewsite.png

drewsite.png

549 ms

happy_computer.gif

happy_computer.gif

124 ms

runtime_v4.png

runtime_v4.png

461 ms

transparent_cheereio_logo.png

transparent_cheereio_logo.png

459 ms

neurath_us_job_change.jpg

neurath_us_job_change.jpg

279 ms

Title.png

Title.png

214 ms

dvd.png

dvd.png

187 ms

rose_cursor.cur

rose_cursor.cur

194 ms

css2

css2

29 ms

variables.js

variables.js

31 ms

2.edcda44d.chunk.js

2.edcda44d.chunk.js

43 ms

main.7276d47b.chunk.js

main.7276d47b.chunk.js

61 ms

gtm.js

gtm.js

44 ms

main.js

main.js

21 ms

Accessibility Review

drewpendergrass.com accessibility score

78

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

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

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

High

Page has valid source maps

SEO Factors

drewpendergrass.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

drewpendergrass.com

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