Tools & Wizards About Us
williamgeorge.net screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

williamgeorge.net

William George Associates – William George Associates

Page Load Speed

8.7 sec in total

First Response

1.2 sec

Resources Loaded

7.1 sec

Page Rendered

509 ms

williamgeorge.net screenshot

About Website

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

Visit williamgeorge.net

Key Findings

We analyzed Williamgeorge.net page load time and found that the first response time was 1.2 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

williamgeorge.net performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

www.williamgeorge.net

1172 ms

sdm_wp_styles.css

56 ms

accessibility.min.css

116 ms

tribe-events-full.min.css

161 ms

tribe-events-pro-full.min.css

169 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 98% of them (107 requests) were addressed to the original Williamgeorge.net, 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Williamgeorge.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.4 kB (40%)

Content Size

790.8 kB

After Optimization

471.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Williamgeorge.net main page is 790.8 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. 65% of websites need less resources to load. HTML takes 345.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 302.0 kB

  • Original 345.1 kB
  • After minification 337.8 kB
  • After compression 43.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. 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 302.0 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.8 kB
  • After minification 5.8 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. William George images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 13.6 kB

  • Original 239.4 kB
  • After minification 238.9 kB
  • After compression 225.8 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

-2%

Potential reduce by 3.8 kB

  • Original 200.4 kB
  • After minification 199.8 kB
  • After compression 196.6 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. Williamgeorge.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 103 (95%)

Requests Now

108

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.williamgeorge.net

www.williamgeorge.net

1172 ms

sdm_wp_styles.css

sdm_wp_styles.css

56 ms

accessibility.min.css

accessibility.min.css

116 ms

tribe-events-full.min.css

tribe-events-full.min.css

161 ms

tribe-events-pro-full.min.css

tribe-events-pro-full.min.css

169 ms

jquery-ui-1.8.23.custom.css

jquery-ui-1.8.23.custom.css

165 ms

bootstrap-datepicker.standalone.min.css

bootstrap-datepicker.standalone.min.css

170 ms

tribe-events-theme.min.css

tribe-events-theme.min.css

164 ms

events-single.min.css

events-single.min.css

173 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

219 ms

dashicons.min.css

dashicons.min.css

215 ms

variables-skeleton.min.css

variables-skeleton.min.css

216 ms

variables-full.min.css

variables-full.min.css

217 ms

common-skeleton.min.css

common-skeleton.min.css

219 ms

common-full.min.css

common-full.min.css

225 ms

tickets.min.css

tickets.min.css

271 ms

rsvp-v1.min.css

rsvp-v1.min.css

269 ms

style.min.css

style.min.css

278 ms

cookie-law-info-public.css

cookie-law-info-public.css

273 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

274 ms

theme-my-login.min.css

theme-my-login.min.css

281 ms

css

css

34 ms

style.min.css

style.min.css

326 ms

style.css

style.css

324 ms

style.css

style.css

333 ms

global.min.css

global.min.css

333 ms

header.min.css

header.min.css

333 ms

content.min.css

content.min.css

334 ms

woocommerce.min.css

woocommerce.min.css

378 ms

footer.min.css

footer.min.css

376 ms

tribe-events.min.css

tribe-events.min.css

384 ms

style.css

style.css

383 ms

rsvp.min.css

rsvp.min.css

384 ms

jquery.min.js

jquery.min.js

389 ms

jquery-migrate.min.js

jquery-migrate.min.js

427 ms

php-date-formatter.min.js

php-date-formatter.min.js

430 ms

cookie-law-info-public.js

cookie-law-info-public.js

431 ms

css

css

29 ms

tooltipster.bundle.min.css

tooltipster.bundle.min.css

425 ms

views-skeleton.min.css

views-skeleton.min.css

390 ms

views-skeleton.min.css

views-skeleton.min.css

334 ms

views-full.min.css

views-full.min.css

333 ms

views-full.min.css

views-full.min.css

330 ms

wc-blocks.css

wc-blocks.css

331 ms

events-virtual-skeleton.min.css

events-virtual-skeleton.min.css

331 ms

events-virtual-full.min.css

events-virtual-full.min.css

329 ms

sdm_wp_scripts.js

sdm_wp_scripts.js

330 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

373 ms

add-to-cart.min.js

add-to-cart.min.js

371 ms

js.cookie.min.js

js.cookie.min.js

372 ms

woocommerce.min.js

woocommerce.min.js

373 ms

events-dynamic.min.js

events-dynamic.min.js

371 ms

rsvp.min.js

rsvp.min.js

362 ms

ticket-details.min.js

ticket-details.min.js

350 ms

theme-my-login.min.js

theme-my-login.min.js

347 ms

hooks.min.js

hooks.min.js

348 ms

i18n.min.js

i18n.min.js

347 ms

url.min.js

url.min.js

339 ms

api-fetch.min.js

api-fetch.min.js

340 ms

ultp.min.js

ultp.min.js

369 ms

navigation.min.js

navigation.min.js

360 ms

sourcebuster.min.js

sourcebuster.min.js

359 ms

order-attribution.min.js

order-attribution.min.js

360 ms

tribe-common.min.js

tribe-common.min.js

355 ms

core.min.js

core.min.js

356 ms

mouse.min.js

mouse.min.js

334 ms

draggable.min.js

draggable.min.js

331 ms

jquery.nanoscroller.min.js

jquery.nanoscroller.min.js

331 ms

week-grid-scroller.min.js

week-grid-scroller.min.js

322 ms

accordion.min.js

accordion.min.js

327 ms

week-day-selector.min.js

week-day-selector.min.js

319 ms

week-multiday-toggle.min.js

week-multiday-toggle.min.js

331 ms

week-event-link.min.js

week-event-link.min.js

335 ms

map-events-scroller.min.js

map-events-scroller.min.js

341 ms

swiper.min.js

swiper.min.js

341 ms

map-no-venue-modal.min.js

map-no-venue-modal.min.js

335 ms

map-provider-google-maps.min.js

map-provider-google-maps.min.js

334 ms

map-events.min.js

map-events.min.js

331 ms

tooltipster.bundle.min.js

tooltipster.bundle.min.js

338 ms

tooltip.min.js

tooltip.min.js

335 ms

tooltip-pro.min.js

tooltip-pro.min.js

337 ms

multiday-events.min.js

multiday-events.min.js

340 ms

multiday-events-pro.min.js

multiday-events-pro.min.js

251 ms

toggle-recurrence.min.js

toggle-recurrence.min.js

291 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

299 ms

datepicker.min.js

datepicker.min.js

297 ms

datepicker-pro.min.js

datepicker-pro.min.js

300 ms

query-string.min.js

query-string.min.js

308 ms

underscore-before.js

underscore-before.js

280 ms

underscore.min.js

underscore.min.js

312 ms

underscore-after.js

underscore-after.js

317 ms

manager.min.js

manager.min.js

319 ms

breakpoints.min.js

breakpoints.min.js

318 ms

viewport.min.js

viewport.min.js

331 ms

view-selector.min.js

view-selector.min.js

303 ms

ical-links.min.js

ical-links.min.js

299 ms

navigation-scroll.min.js

navigation-scroll.min.js

294 ms

month-mobile-events.min.js

month-mobile-events.min.js

297 ms

month-grid.min.js

month-grid.min.js

297 ms

events-bar.min.js

events-bar.min.js

311 ms

events-bar-inputs.min.js

events-bar-inputs.min.js

292 ms

wsm_new.js

wsm_new.js

340 ms

WGA-logo-for-Website-rounded-1.png

WGA-logo-for-Website-rounded-1.png

338 ms

Home-Page-Pic-Rev-0824-scaled-e1663699751292-jpg.webp

Home-Page-Pic-Rev-0824-scaled-e1663699751292-jpg.webp

386 ms

www.williamgeorge.net

www.williamgeorge.net

3576 ms

tribe-events-full-mobile.min.css

tribe-events-full-mobile.min.css

65 ms

tribe-events-theme-mobile.min.css

tribe-events-theme-mobile.min.css

61 ms

views-print.min.css

views-print.min.css

58 ms

views-print.min.css

views-print.min.css

55 ms

Accessibility Review

williamgeorge.net accessibility score

90

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

Links do not have a discernible name

Best Practices

williamgeorge.net 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

williamgeorge.net SEO score

78

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

robots.txt is not valid

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

williamgeorge.net

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