Tools & Wizards About Us
hometownlocator.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

hometownlocator.com

State Gazetteer: Boundary Maps, Demographic Data, for 343,374 Communities

Page Load Speed

1.1 sec in total

First Response

24 ms

Resources Loaded

932 ms

Page Rendered

124 ms

hometownlocator.com screenshot

About Website

Click here to check amazing Hometownlocator content for United States. Otherwise, check out these important facts you probably never knew about hometownlocator.com

State gazetteers with profiles for 343,374 communities. Profiles include a boundary map, current demographic data, school zones, and the most popular nearby places..

Visit hometownlocator.com

Key Findings

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

Performance Metrics

hometownlocator.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

hometownlocator.com

24 ms

www.hometownlocator.com

274 ms

gppstub.js

70 ms

boise.js

66 ms

abilene.js

50 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 66% of them (27 requests) were addressed to the original Hometownlocator.com, 5% (2 requests) were made to The.gatekeeperconsent.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (274 ms) belongs to the original domain Hometownlocator.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 409.6 kB (45%)

Content Size

900.2 kB

After Optimization

490.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Hometownlocator.com main page is 900.2 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. 45% of websites need less resources to load. HTML takes 464.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 393.8 kB

  • Original 464.7 kB
  • After minification 464.7 kB
  • After compression 70.9 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 393.8 kB or 85% of the original size.

JavaScript Optimization

-4%

Potential reduce by 15.8 kB

  • Original 430.0 kB
  • After minification 429.9 kB
  • After compression 414.2 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

-1%

Potential reduce by 31 B

  • Original 5.5 kB
  • After minification 5.5 kB
  • After compression 5.5 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. Hometownlocator.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (85%)

Requests Now

39

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hometownlocator.com

hometownlocator.com

24 ms

www.hometownlocator.com

www.hometownlocator.com

274 ms

gppstub.js

gppstub.js

70 ms

boise.js

boise.js

66 ms

abilene.js

abilene.js

50 ms

tulsa.js

tulsa.js

46 ms

et.js

et.js

46 ms

js

js

75 ms

ezvideojscss.css

ezvideojscss.css

58 ms

ezvideojspluginscss.css

ezvideojspluginscss.css

117 ms

vtt.min.js

vtt.min.js

44 ms

ccpaplus.js

ccpaplus.js

61 ms

mapsjs-core.js

mapsjs-core.js

52 ms

mapsjs-service.js

mapsjs-service.js

58 ms

screx.js

screx.js

21 ms

mulvane.js

mulvane.js

22 ms

wichita.js

wichita.js

14 ms

raleigh.js

raleigh.js

203 ms

vista.js

vista.js

24 ms

olathe.js

olathe.js

182 ms

axolotl.js

axolotl.js

193 ms

lazy_load.js

lazy_load.js

191 ms

js

js

53 ms

quant.js

quant.js

78 ms

tortoise.js

tortoise.js

64 ms

css_onload.js

css_onload.js

69 ms

script_delay.js

script_delay.js

150 ms

recommended_pages.js

recommended_pages.js

67 ms

vitals.js

vitals.js

68 ms

drake.js

drake.js

67 ms

chanute.js

chanute.js

76 ms

jellyfish.js

jellyfish.js

77 ms

analytics.js

analytics.js

45 ms

us_www.css

us_www.css

18 ms

media-queries.css

media-queries.css

33 ms

rules-p-famXfNfcmlM8g.js

rules-p-famXfNfcmlM8g.js

30 ms

collect

collect

18 ms

pixel;r=1762233151;rf=0;a=p-famXfNfcmlM8g;url=https%3A%2F%2Fwww.hometownlocator.com%2F;uht=2;fpan=1;fpa=P0-1416351045-1714837479908;pbc=;ns=0;ce=1;qjs=1;qv=b70d35e8-20231208114759;cm=;gdpr=0;ref=;d=hometownlocator.com;dst=0;et=1714837479964;tzo=-180;ogl=;ses=b54aa456-a918-4a14-8cb8-7c431e30db98;mdl=

pixel;r=1762233151;rf=0;a=p-famXfNfcmlM8g;url=https%3A%2F%2Fwww.hometownlocator.com%2F;uht=2;fpan=1;fpa=P0-1416351045-1714837479908;pbc=;ns=0;ce=1;qjs=1;qv=b70d35e8-20231208114759;cm=;gdpr=0;ref=;d=hometownlocator.com;dst=0;et=1714837479964;tzo=-180;ogl=;ses=b54aa456-a918-4a14-8cb8-7c431e30db98;mdl=

25 ms

collect

collect

12 ms

www_print.css

www_print.css

14 ms

ga-audiences

ga-audiences

76 ms

Accessibility Review

hometownlocator.com accessibility score

77

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.

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

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

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

hometownlocator.com SEO score

93

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

Image elements do not have [alt] attributes

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

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

hometownlocator.com

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