Tools & Wizards About Us
communityremarks.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 0

    Best Practices

  • 79

    SEO

    Google-friendlier than
    40% of websites

communityremarks.com

Community Engagement for Community Remarks | Your online community engagement platform - Community Remarks

Page Load Speed

6.9 sec in total

First Response

1.1 sec

Resources Loaded

5.3 sec

Page Rendered

554 ms

communityremarks.com screenshot

About Website

Visit communityremarks.com now to see the best up-to-date Community Remarks content and also check out these interesting facts you probably never knew about communityremarks.com

Community Remarks is a survey map that makes it easy for citizens to access a map, plot a comment, and go. Make planning maps engaging and interactive.

Visit communityremarks.com

Key Findings

We analyzed Communityremarks.com page load time and found that the first response time was 1.1 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

communityremarks.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value1,470 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

communityremarks.com

1088 ms

wp-emoji-release.min.js

84 ms

style.min.css

124 ms

styles.css

152 ms

sfsi-style.css

120 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 68% of them (65 requests) were addressed to the original Communityremarks.com, 7% (7 requests) were made to Static.olark.com and 7% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Communityremarks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 815.8 kB (22%)

Content Size

3.7 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Communityremarks.com main page is 3.7 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. Only a small number of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 87.2 kB

  • Original 111.1 kB
  • After minification 109.7 kB
  • After compression 23.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 87.2 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 167.2 kB

  • Original 2.2 MB
  • After minification 2.1 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. Community Remarks images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 63.6 kB

  • Original 558.0 kB
  • After minification 557.9 kB
  • After compression 494.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 63.6 kB or 11% of the original size.

CSS Optimization

-65%

Potential reduce by 497.8 kB

  • Original 765.4 kB
  • After minification 730.5 kB
  • After compression 267.6 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. Communityremarks.com needs all CSS files to be minified and compressed as it can save up to 497.8 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (67%)

Requests Now

86

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

communityremarks.com

communityremarks.com

1088 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

84 ms

style.min.css

style.min.css

124 ms

styles.css

styles.css

152 ms

sfsi-style.css

sfsi-style.css

120 ms

front-styles.css

front-styles.css

167 ms

js_composer.min.css

js_composer.min.css

169 ms

css

css

33 ms

main.min.css

main.min.css

227 ms

font-awesome.min.css

font-awesome.min.css

185 ms

fontello.min.css

fontello.min.css

200 ms

post-type.css

post-type.css

222 ms

custom-443da2206f.css

custom-443da2206f.css

346 ms

media-a85feb3ac1.css

media-a85feb3ac1.css

276 ms

post-type-dynamic-ac80b52e23.css

post-type-dynamic-ac80b52e23.css

265 ms

style.css

style.css

277 ms

Defaults.css

Defaults.css

330 ms

jquery.min.js

jquery.min.js

333 ms

jquery-migrate.min.js

jquery-migrate.min.js

341 ms

above-the-fold.min.js

above-the-fold.min.js

384 ms

js

js

68 ms

vc_linecons_icons.min.css

vc_linecons_icons.min.css

432 ms

css

css

44 ms

animate.min.css

animate.min.css

523 ms

js_composer_tta.min.css

js_composer_tta.min.css

523 ms

main.min.js

main.min.js

524 ms

index.js

index.js

519 ms

index.js

index.js

523 ms

core.min.js

core.min.js

523 ms

modernizr.custom.min.js

modernizr.custom.min.js

523 ms

jquery.shuffle.min.js

jquery.shuffle.min.js

548 ms

random-shuffle-min.js

random-shuffle-min.js

550 ms

custom.js

custom.js

568 ms

page-preloader.js

page-preloader.js

567 ms

post-type.js

post-type.js

549 ms

js_composer_front.min.js

js_composer_front.min.js

840 ms

vc-waypoints.min.js

vc-waypoints.min.js

632 ms

vc-accordion.min.js

vc-accordion.min.js

840 ms

vc-tta-autoplay.min.js

vc-tta-autoplay.min.js

839 ms

analytics.js

analytics.js

117 ms

piwik.js

piwik.js

439 ms

loader.js

loader.js

116 ms

contactus.php

contactus.php

424 ms

archers.gif

archers.gif

417 ms

CR_refesh_web_transparent-1.png

CR_refesh_web_transparent-1.png

417 ms

CR_refesh_mobile_transparent.png

CR_refesh_mobile_transparent.png

420 ms

placemarker_transparent.png

placemarker_transparent.png

418 ms

ideas3.png

ideas3.png

418 ms

transportation_trasparent.png

transportation_trasparent.png

419 ms

bike_ped_plan.png

bike_ped_plan.png

501 ms

bus_routes.png

bus_routes.png

500 ms

wayfinding_plan.png

wayfinding_plan.png

500 ms

landusedemo_commentmap-1024x767.png

landusedemo_commentmap-1024x767.png

657 ms

hands_up_optimized4.png

hands_up_optimized4.png

689 ms

default_facebook.png

default_facebook.png

499 ms

icon_Visit_us_en_US.png

icon_Visit_us_en_US.png

665 ms

en_US.svg

en_US.svg

666 ms

default_twitter.png

default_twitter.png

665 ms

en_US_Follow.svg

en_US_Follow.svg

663 ms

default_youtube.png

default_youtube.png

750 ms

default_linkedin.png

default_linkedin.png

720 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

25 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

24 ms

app.js

app.js

21 ms

collect

collect

87 ms

5748-531-10-4216.js

5748-531-10-4216.js

281 ms

sdk.js

sdk.js

272 ms

js

js

208 ms

jquery-3.1.1.slim.min.js

jquery-3.1.1.slim.min.js

256 ms

bootstrap.min.js

bootstrap.min.js

407 ms

bootstrap.min.css

bootstrap.min.css

429 ms

jquery-ui-1.10.2.custom.min.js

jquery-ui-1.10.2.custom.min.js

411 ms

jquery-ui-1.10.3.custom.min.css

jquery-ui-1.10.3.custom.min.css

440 ms

api.js

api.js

246 ms

vc_linecons.woff

vc_linecons.woff

402 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

255 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

268 ms

sdk.js

sdk.js

62 ms

c

c

276 ms

application2.js

application2.js

24 ms

piwik.php

piwik.php

3294 ms

74 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

208 ms

storage.html

storage.html

38 ms

storage.js

storage.js

2 ms

visits

visits

145 ms

recaptcha__en.js

recaptcha__en.js

27 ms

fallback

fallback

26 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

18 ms

logo_48.png

logo_48.png

4 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

3 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

14 ms

theme.css

theme.css

3 ms

16by16.ico

16by16.ico

67 ms

Accessibility Review

communityremarks.com accessibility score

66

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

communityremarks.com SEO score

79

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

communityremarks.com

Open Graph data is detected on the main page of Community Remarks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: