Tools & Wizards About Us
briankelm.net screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

briankelm.net

Brian Kelm Productions

Page Load Speed

1.6 sec in total

First Response

103 ms

Resources Loaded

642 ms

Page Rendered

842 ms

briankelm.net screenshot

About Website

Visit briankelm.net now to see the best up-to-date Brian Kelm content and also check out these interesting facts you probably never knew about briankelm.net

Brian Kelm is an experienced master of ceremonies and master certified wedding planner. Brian plans, produces and entertains at hundreds of weddings, corporate events and private parties every year. H...

Visit briankelm.net

Key Findings

We analyzed Briankelm.net page load time and found that the first response time was 103 ms and then it took 1.5 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

briankelm.net performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

briankelm.net

103 ms

briankelm.net

350 ms

regular.css

77 ms

solid.css

87 ms

brands.css

95 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 11% of them (2 requests) were addressed to the original Briankelm.net, 56% (10 requests) were made to Assets.cdn.filesafe.space and 17% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (350 ms) belongs to the original domain Briankelm.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 411.8 kB (15%)

Content Size

2.8 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-85%

Potential reduce by 353.9 kB

  • Original 418.1 kB
  • After minification 372.4 kB
  • After compression 64.2 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 45.8 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 353.9 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 57.6 kB

  • Original 2.4 MB
  • After minification 2.3 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. Brian Kelm images are well optimized though.

CSS Optimization

-10%

Potential reduce by 260 B

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 2.4 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. Briankelm.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

16

After Optimization

12

  • Images
  • CSS

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

Network Requests Diagram

briankelm.net

briankelm.net

103 ms

briankelm.net

briankelm.net

350 ms

regular.css

regular.css

77 ms

solid.css

solid.css

87 ms

brands.css

brands.css

95 ms

element_animation.css

element_animation.css

75 ms

css

css

77 ms

65e6563cf0560514920b6c1f.jpeg

65e6563cf0560514920b6c1f.jpeg

140 ms

64ed1cae2a69ce7d4f69917e.jpeg

64ed1cae2a69ce7d4f69917e.jpeg

112 ms

65e6563cc72662765edd0042.png

65e6563cc72662765edd0042.png

158 ms

64ee20f0d8a4acf2733735a9.jpeg

64ee20f0d8a4acf2733735a9.jpeg

80 ms

64ee20f0d8a4ac4d663735aa.jpeg

64ee20f0d8a4ac4d663735aa.jpeg

119 ms

64ee20f0d8a4ac3d8f3735a4.jpeg

64ee20f0d8a4ac3d8f3735a4.jpeg

202 ms

64ed1caeee3907470f0f75d9.jpeg

64ed1caeee3907470f0f75d9.jpeg

90 ms

64ee2793ba2ab033d573e646.png

64ee2793ba2ab033d573e646.png

91 ms

64ee0bd2ba2ab0b6f2737872.jpeg

64ee0bd2ba2ab0b6f2737872.jpeg

179 ms

62ad701731040304329f5f36.png

62ad701731040304329f5f36.png

124 ms

payment-warning.dd3003de.svg

payment-warning.dd3003de.svg

12 ms

Accessibility Review

briankelm.net accessibility score

97

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.

Best Practices

briankelm.net best practices score

75

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

briankelm.net SEO score

95

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

briankelm.net

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