Tools & Wizards About Us
localdata.com screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

localdata.com

Better data makes better cities | LocalData - Better data makes beter cities

Page Load Speed

492 ms in total

First Response

21 ms

Resources Loaded

177 ms

Page Rendered

294 ms

localdata.com screenshot

About Website

Click here to check amazing Local Data content. Otherwise, check out these important facts you probably never knew about localdata.com

Collect the place-based data you need using our easy mobile tools and web dashboard. Create your own survey or engage around community health, safety, commercial development, blight, historic resource...

Visit localdata.com

Key Findings

We analyzed Localdata.com page load time and found that the first response time was 21 ms and then it took 471 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

localdata.com performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.2 s

95/100

10%

Network Requests Diagram

localdata.com

21 ms

app.css

22 ms

jquery.min.js

9 ms

app.js

15 ms

map.png

19 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 88% of them (28 requests) were addressed to the original Localdata.com, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (117 ms) belongs to the original domain Localdata.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 265.0 kB (31%)

Content Size

866.6 kB

After Optimization

601.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Localdata.com main page is 866.6 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. 40% of websites need less resources to load. Images take 804.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 8.7 kB

  • Original 12.0 kB
  • After minification 9.5 kB
  • After compression 3.3 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.4 kB, which is 20% 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 8.7 kB or 72% of the original size.

Image Optimization

-32%

Potential reduce by 256.3 kB

  • Original 804.5 kB
  • After minification 548.2 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. Obviously, Local Data needs image optimization as it can save up to 256.3 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 50.1 kB
  • After minification 50.1 kB
  • After compression 50.1 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.

Requests Breakdown

We found no issues to fix!

Requests Now

28

After Optimization

28

  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Local Data. According to our analytics all requests are already optimized.

Network Requests Diagram

localdata.com

localdata.com

21 ms

app.css

app.css

22 ms

jquery.min.js

jquery.min.js

9 ms

app.js

app.js

15 ms

map.png

map.png

19 ms

checks.png

checks.png

11 ms

editor.png

editor.png

21 ms

future-of-cities.png

future-of-cities.png

29 ms

planetizen-logo_lightened.png

planetizen-logo_lightened.png

31 ms

placeeconomics-logo_lightened.png

placeeconomics-logo_lightened.png

34 ms

harvard_logo_lightened.png

harvard_logo_lightened.png

29 ms

mapc_logo_lightened.png

mapc_logo_lightened.png

27 ms

UChicago_gray_lightened.png

UChicago_gray_lightened.png

113 ms

houston_seal_lightened.png

houston_seal_lightened.png

115 ms

wayne_wordmark_lightened.png

wayne_wordmark_lightened.png

116 ms

detroit-seal_lightened.png

detroit-seal_lightened.png

38 ms

fastcodesign_logo_dark_lightened.png

fastcodesign_logo_dark_lightened.png

37 ms

datadrivenjournalism-logo_lightened.png

datadrivenjournalism-logo_lightened.png

46 ms

newfront-niemanlab-biglogo2_lightened.png

newfront-niemanlab-biglogo2_lightened.png

115 ms

strata-logo_lightened.png

strata-logo_lightened.png

114 ms

logo-all-points2_lightened.png

logo-all-points2_lightened.png

117 ms

b.min.js

b.min.js

87 ms

ga.js

ga.js

59 ms

dotgrid-white.png

dotgrid-white.png

19 ms

bg4.jpg

bg4.jpg

18 ms

logo.png

logo.png

19 ms

arrow.png

arrow.png

18 ms

iphone.png

iphone.png

28 ms

graphs.svg

graphs.svg

16 ms

bold.woff

bold.woff

19 ms

regular.woff

regular.woff

30 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

localdata.com accessibility score

60

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.

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

Links do not have a discernible name

Best Practices

localdata.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

localdata.com SEO score

92

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

localdata.com

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