Tools & Wizards About Us
homeanthology.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

homeanthology.com

Home Anthology - Home

Page Load Speed

755 ms in total

First Response

49 ms

Resources Loaded

457 ms

Page Rendered

249 ms

homeanthology.com screenshot

About Website

Visit homeanthology.com now to see the best up-to-date Home Anthology content for United States and also check out these interesting facts you probably never knew about homeanthology.com

Visit homeanthology.com

Key Findings

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

Performance Metrics

homeanthology.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.139

79/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

www.homeanthology.com

49 ms

common.css

27 ms

squarespace-gallery-slideshow.css

26 ms

yahoo-dom-event.js

33 ms

connection_core-min.js

26 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 83% of them (24 requests) were addressed to the original Homeanthology.com, 7% (2 requests) were made to Static1.1.sqspcdn.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (147 ms) relates to the external source Ajax.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 257.4 kB (59%)

Content Size

435.1 kB

After Optimization

177.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Homeanthology.com main page is 435.1 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. 25% of websites need less resources to load. Javascripts take 246.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 15.8 kB

  • Original 19.9 kB
  • After minification 17.3 kB
  • After compression 4.0 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 2.6 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 15.8 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 2.7 kB

  • Original 106.3 kB
  • After minification 103.5 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. Home Anthology images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 185.6 kB

  • Original 246.1 kB
  • After minification 209.5 kB
  • After compression 60.4 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 185.6 kB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 53.1 kB

  • Original 62.9 kB
  • After minification 50.8 kB
  • After compression 9.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. Homeanthology.com needs all CSS files to be minified and compressed as it can save up to 53.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (56%)

Requests Now

27

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.homeanthology.com

www.homeanthology.com

49 ms

common.css

common.css

27 ms

squarespace-gallery-slideshow.css

squarespace-gallery-slideshow.css

26 ms

yahoo-dom-event.js

yahoo-dom-event.js

33 ms

connection_core-min.js

connection_core-min.js

26 ms

json-min.js

json-min.js

25 ms

animation-min.js

animation-min.js

25 ms

selector.js

selector.js

54 ms

element.js

element.js

62 ms

global.js

global.js

75 ms

lightbox.js

lightbox.js

51 ms

api.js

api.js

52 ms

base64.js

base64.js

52 ms

census.js

census.js

72 ms

yui2-yui3-bridge.js

yui2-yui3-bridge.js

71 ms

squarespace-gallery-slideshow.js

squarespace-gallery-slideshow.js

85 ms

cookie-min.js

cookie-min.js

101 ms

eu-cookie-policy.js

eu-cookie-policy.js

103 ms

webfont.js

webfont.js

147 ms

RecordHit

RecordHit

27 ms

edge.png

edge.png

28 ms

facebook.png

facebook.png

20 ms

css

css

24 ms

AvantBannerFMLTM3.gif

AvantBannerFMLTM3.gif

55 ms

HomeShot.jpg

HomeShot.jpg

112 ms

RJMlAoFXXQEzZoMSUteGWD8E0i7KZn-EPnyo3HZu7kw.woff

RJMlAoFXXQEzZoMSUteGWD8E0i7KZn-EPnyo3HZu7kw.woff

5 ms

loading.gif

loading.gif

15 ms

overlay-arrow-left.png

overlay-arrow-left.png

13 ms

overlay-arrow-right.png

overlay-arrow-right.png

13 ms

Accessibility Review

homeanthology.com accessibility score

87

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

Links do not have a discernible name

Best Practices

homeanthology.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

homeanthology.com SEO score

69

Search Engine Optimization Advices

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

homeanthology.com

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