Tools & Wizards About Us
hilliard.ws screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hilliard.ws

WEBSITE.WS - Your Internet Address For Life™

Page Load Speed

5.9 sec in total

First Response

262 ms

Resources Loaded

5.1 sec

Page Rendered

561 ms

hilliard.ws screenshot

About Website

Visit hilliard.ws now to see the best up-to-date Hilliard content and also check out these interesting facts you probably never knew about hilliard.ws

Adding character and humor to an otherwise drab world wide web - Celebrating a presence on the web since 1996

Visit hilliard.ws

Key Findings

We analyzed Hilliard.ws page load time and found that the first response time was 262 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

hilliard.ws performance score

0

Network Requests Diagram

rhilliard.net

262 ms

styles.css

120 ms

fonts.css

2863 ms

logo.css

2934 ms

minimized.css

3110 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hilliard.ws, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Rhilliard.net.

Page Optimization Overview & Recommendations

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

Content Size

2.4 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 27.1 kB

  • Original 34.2 kB
  • After minification 25.4 kB
  • After compression 7.1 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.8 kB, which is 26% 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.1 kB or 79% of the original size.

Image Optimization

-13%

Potential reduce by 249.5 kB

  • Original 1.9 MB
  • After minification 1.6 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, Hilliard needs image optimization as it can save up to 249.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 274.3 kB

  • Original 382.8 kB
  • After minification 360.6 kB
  • After compression 108.6 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 274.3 kB or 72% of the original size.

CSS Optimization

-88%

Potential reduce by 64.3 kB

  • Original 72.7 kB
  • After minification 42.7 kB
  • After compression 8.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. Hilliard.ws needs all CSS files to be minified and compressed as it can save up to 64.3 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rhilliard.net

rhilliard.net

262 ms

styles.css

styles.css

120 ms

fonts.css

fonts.css

2863 ms

logo.css

logo.css

2934 ms

minimized.css

minimized.css

3110 ms

mega-menu.css

mega-menu.css

3187 ms

responsive.css

responsive.css

3240 ms

jquery-1.5.1.min.js

jquery-1.5.1.min.js

206 ms

jquery.cookie.js

jquery.cookie.js

274 ms

pxgradient-1.0.1.jquery.js

pxgradient-1.0.1.jquery.js

342 ms

jquery-ui-1.8.11.custom.min.js

jquery-ui-1.8.11.custom.min.js

489 ms

special_functions.js

special_functions.js

561 ms

hoverIntent.js

hoverIntent.js

632 ms

superfish.js

superfish.js

704 ms

webwidget_slideshow_common.js

webwidget_slideshow_common.js

781 ms

css

css

31 ms

css

css

16 ms

nivo_slider_small.css

nivo_slider_small.css

71 ms

body_bg.jpg

body_bg.jpg

142 ms

minimized_bg.jpg

minimized_bg.jpg

271 ms

globe.png

globe.png

327 ms

robert-hilliard-banner.png

robert-hilliard-banner.png

171 ms

twitter_icon2.png

twitter_icon2.png

100 ms

facebook_icon2.png

facebook_icon2.png

98 ms

photo_icon.png

photo_icon.png

128 ms

movies_icon.png

movies_icon.png

127 ms

kite_icon.png

kite_icon.png

191 ms

articles_icon.png

articles_icon.png

189 ms

bio_icon.png

bio_icon.png

268 ms

triphilliard_kite500.png

triphilliard_kite500.png

396 ms

enthus_icon.png

enthus_icon.png

297 ms

hobbies_icon.png

hobbies_icon.png

299 ms

passion_icon.png

passion_icon.png

341 ms

triphilliard_goldwing500.png

triphilliard_goldwing500.png

588 ms

tv_icon.png

tv_icon.png

405 ms

video_icon.png

video_icon.png

354 ms

history_icon.png

history_icon.png

535 ms

motorcycle_icon.png

motorcycle_icon.png

420 ms

world_sm.png

world_sm.png

422 ms

linkedin_icon2.png

linkedin_icon2.png

477 ms

googleplus_icon2.png

googleplus_icon2.png

467 ms

pinterest_icon2.png

pinterest_icon2.png

485 ms

youtube_icon2.png

youtube_icon2.png

491 ms

flickr_icon2.png

flickr_icon2.png

531 ms

triphilliard_200.png

triphilliard_200.png

552 ms

latest_news_ticker.png

latest_news_ticker.png

530 ms

columns_top.png

columns_top.png

645 ms

columns_bg.png

columns_bg.png

783 ms

columns_bottom.png

columns_bottom.png

1346 ms

footer_bg.jpg

footer_bg.jpg

598 ms

footer.jpg

footer.jpg

828 ms

footer_separator.png

footer_separator.png

628 ms

footer_quicklinks.png

footer_quicklinks.png

662 ms

footer_quicklist.png

footer_quicklist.png

696 ms

nvC8O-FhgKFS_js6E2VB9w.ttf

nvC8O-FhgKFS_js6E2VB9w.ttf

26 ms

analytics.js

analytics.js

30 ms

footer_contact.png

footer_contact.png

630 ms

footer_social.png

footer_social.png

659 ms

collect

collect

14 ms

collect

collect

77 ms

SEO Factors

hilliard.ws SEO score

0

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 Hilliard.ws 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 Hilliard.ws 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

hilliard.ws

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