Tools & Wizards About Us
merriam.org screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

merriam.org

Home City of Merriam

Page Load Speed

2.1 sec in total

First Response

425 ms

Resources Loaded

1.4 sec

Page Rendered

239 ms

merriam.org screenshot

About Website

Welcome to merriam.org homepage info - get ready to check Merriam best content for United States right away, or after learning these important things about merriam.org

Merriam is a welcoming, peaceful, tight-knit community that is small in size, but big at heart. Our residents enjoy a wide variety of amenities and services including beautiful tree-lined streets, wal...

Visit merriam.org

Key Findings

We analyzed Merriam.org page load time and found that the first response time was 425 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

merriam.org performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

merriam.org

425 ms

10593317.css

140 ms

-1795492207.js

211 ms

1127434005.js

75 ms

-212365995.js

166 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 96% of them (73 requests) were addressed to the original Merriam.org, 3% (2 requests) were made to Code.jquery.com and 1% (1 request) were made to Analytics.civicplus.com. The less responsive or slowest element that took the longest time to load (544 ms) belongs to the original domain Merriam.org.

Page Optimization Overview & Recommendations

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

Content Size

1.9 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 52.9 kB

  • Original 69.2 kB
  • After minification 64.8 kB
  • After compression 16.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. 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 52.9 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 48.1 kB

  • Original 1.3 MB
  • After minification 1.3 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. Merriam images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 392.9 kB

  • Original 481.8 kB
  • After minification 353.9 kB
  • After compression 88.9 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 392.9 kB or 82% of the original size.

CSS Optimization

-51%

Potential reduce by 6.6 kB

  • Original 12.9 kB
  • After minification 12.1 kB
  • After compression 6.3 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. Merriam.org needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 51% of the original size.

Requests Breakdown

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

Requests Now

74

After Optimization

63

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

merriam.org

merriam.org

425 ms

10593317.css

10593317.css

140 ms

-1795492207.js

-1795492207.js

211 ms

1127434005.js

1127434005.js

75 ms

-212365995.js

-212365995.js

166 ms

WebResource.axd

WebResource.axd

92 ms

ScriptResource.axd

ScriptResource.axd

127 ms

FeatureAreaSearchAutoComplete.css

FeatureAreaSearchAutoComplete.css

96 ms

jquery-ui.css

jquery-ui.css

40 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

139 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

140 ms

jquery.ui.position.min.js

jquery.ui.position.min.js

154 ms

jquery.ui.autocomplete.min.js

jquery.ui.autocomplete.min.js

166 ms

MouseOverMenu.js

MouseOverMenu.js

210 ms

-1992112027.js

-1992112027.js

146 ms

Path

Path

544 ms

HomeModuleIconLarge.png

HomeModuleIconLarge.png

59 ms

DashboardShot.png

DashboardShot.png

52 ms

currentweather.png

currentweather.png

54 ms

bb.jpg

bb.jpg

88 ms

ExploreMerriam.jpg

ExploreMerriam.jpg

87 ms

ResidentResources.jpg

ResidentResources.jpg

96 ms

DoingBusiness.jpg

DoingBusiness.jpg

98 ms

CityGovernment.jpg

CityGovernment.jpg

97 ms

HowDoI.jpg

HowDoI.jpg

142 ms

homeHP.jpg

homeHP.jpg

144 ms

shareHP.jpg

shareHP.jpg

145 ms

icon-close.gif

icon-close.gif

141 ms

rssHP.jpg

rssHP.jpg

146 ms

printHP.jpg

printHP.jpg

164 ms

emailHP.jpg

emailHP.jpg

164 ms

hptabs_news2.png

hptabs_news2.png

188 ms

hptabs_calendar.png

hptabs_calendar.png

187 ms

viewall.png

viewall.png

183 ms

CRT-SPOTLIGHT.jpg

CRT-SPOTLIGHT.jpg

232 ms

fallsHP.jpg

fallsHP.jpg

296 ms

gohp.jpg

gohp.jpg

222 ms

meetingsHP.jpg

meetingsHP.jpg

229 ms

notifymeHP.jpg

notifymeHP.jpg

227 ms

citycodeHP.jpg

citycodeHP.jpg

259 ms

communityalertsHP.jpg

communityalertsHP.jpg

260 ms

navbtm_faqs.png

navbtm_faqs.png

266 ms

navbtm_links_modified.png

navbtm_links_modified.png

267 ms

navbtm_info.png

navbtm_info.png

292 ms

navbtm_sm.png

navbtm_sm.png

304 ms

footer_youtube.png

footer_youtube.png

302 ms

footer_twitter.png

footer_twitter.png

308 ms

footer_facebook.png

footer_facebook.png

333 ms

GlobalToolbarBkg.png

GlobalToolbarBkg.png

330 ms

ButtonRightBkg.png

ButtonRightBkg.png

310 ms

ButtonLeftBkg.png

ButtonLeftBkg.png

294 ms

shdwbkg.jpg

shdwbkg.jpg

293 ms

shdbkg.jpg

shdbkg.jpg

315 ms

topbkg.jpg

topbkg.jpg

377 ms

shdbkgbot.jpg

shdbkgbot.jpg

291 ms

bc.jpg

bc.jpg

283 ms

ExploreMerriam2.jpg

ExploreMerriam2.jpg

284 ms

ResidentResources2.jpg

ResidentResources2.jpg

318 ms

DoingBusiness2.jpg

DoingBusiness2.jpg

311 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

20 ms

CityGovernment2.jpg

CityGovernment2.jpg

268 ms

HowDoI2.jpg

HowDoI2.jpg

270 ms

tblbkgHP.jpg

tblbkgHP.jpg

304 ms

tbltopHP.jpg

tbltopHP.jpg

305 ms

tblbtmHP.jpg

tblbtmHP.jpg

306 ms

leftnavbkgHP.png

leftnavbkgHP.png

283 ms

footer.jpg

footer.jpg

306 ms

foggyHP.jpg

foggyHP.jpg

366 ms

parkHP.jpg

parkHP.jpg

358 ms

poolHP.jpg

poolHP.jpg

355 ms

carshow1HP.jpg

carshow1HP.jpg

358 ms

carshow2HP.jpg

carshow2HP.jpg

322 ms

boatsHP.jpg

boatsHP.jpg

416 ms

concertHP.jpg

concertHP.jpg

357 ms

instrumentHP.jpg

instrumentHP.jpg

330 ms

piwik.js

piwik.js

131 ms

Accessibility Review

merriam.org accessibility score

100

Accessibility Issues

Best Practices

merriam.org best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

merriam.org SEO score

93

Search Engine Optimization Advices

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

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 Merriam.org 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 Merriam.org 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

merriam.org

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