Tools & Wizards About Us
accessfayetteville.org screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

accessfayetteville.org

Fayetteville, AR - Official Website | Official Website

Page Load Speed

2.3 sec in total

First Response

85 ms

Resources Loaded

1.8 sec

Page Rendered

420 ms

accessfayetteville.org screenshot

About Website

Click here to check amazing Access Fayetteville content for United States. Otherwise, check out these important facts you probably never knew about accessfayetteville.org

Official website for the City of Fayetteville, Arkansas. Learn about all departments, city services and events. Pay utility bills, report concerns, apply for permits, sign up for notifications, view c...

Visit accessfayetteville.org

Key Findings

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

Performance Metrics

accessfayetteville.org performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value43.6 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value1,460 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

accessfayetteville.org

85 ms

www.fayetteville-ar.gov

493 ms

370557728.css

157 ms

-1044733344.css

96 ms

jquery-1.6.4.min.js

210 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Accessfayetteville.org, 56% (38 requests) were made to Fayetteville-ar.gov and 21% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (493 ms) relates to the external source Fayetteville-ar.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.9 kB (13%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Accessfayetteville.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.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 63.3 kB

  • Original 79.3 kB
  • After minification 74.6 kB
  • After compression 16.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. 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 63.3 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 14.3 kB

  • Original 1.5 MB
  • After minification 1.4 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. Access Fayetteville images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 174.8 kB

  • Original 346.2 kB
  • After minification 314.5 kB
  • After compression 171.5 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 174.8 kB or 50% of the original size.

CSS Optimization

-21%

Potential reduce by 2.5 kB

  • Original 12.1 kB
  • After minification 11.5 kB
  • After compression 9.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. Accessfayetteville.org needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (59%)

Requests Now

51

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

accessfayetteville.org

accessfayetteville.org

85 ms

www.fayetteville-ar.gov

www.fayetteville-ar.gov

493 ms

370557728.css

370557728.css

157 ms

-1044733344.css

-1044733344.css

96 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

210 ms

-1549557803.js

-1549557803.js

177 ms

jquery.ui.autocomplete.min.js

jquery.ui.autocomplete.min.js

99 ms

Search.js

Search.js

83 ms

jquery-ui.css

jquery-ui.css

39 ms

Carousel.jquery.js

Carousel.jquery.js

154 ms

Easing.1.3.jquery.js

Easing.1.3.jquery.js

126 ms

2070593296.css

2070593296.css

102 ms

-789272649.js

-789272649.js

228 ms

element.js

element.js

38 ms

Document

Document

75 ms

Path

Path

49 ms

Path

Path

49 ms

Path

Path

46 ms

Path

Path

48 ms

Path

Path

70 ms

Path

Path

80 ms

Document

Document

83 ms

Document

Document

83 ms

INVASIVE.jpg

INVASIVE.jpg

204 ms

Document

Document

96 ms

Path

Path

40 ms

Path

Path

45 ms

Path

Path

54 ms

Path

Path

52 ms

Path

Path

131 ms

Path

Path

133 ms

quo.debug.js

quo.debug.js

135 ms

MediaFramework.js

MediaFramework.js

135 ms

translateelement.css

translateelement.css

54 ms

main.js

main.js

129 ms

analytics.js

analytics.js

60 ms

HiddenMainSubMenus

HiddenMainSubMenus

179 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

45 ms

Message

Message

70 ms

css

css

39 ms

element_main.js

element_main.js

73 ms

collect

collect

25 ms

collect

collect

110 ms

quo.debug.js

quo.debug.js

83 ms

W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf

W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf

62 ms

OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf

OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf

63 ms

7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf

7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf

74 ms

12mE4jfMSBTmg-81EiS-YS3USBnSvpkopQaUR-2r7iU.ttf

12mE4jfMSBTmg-81EiS-YS3USBnSvpkopQaUR-2r7iU.ttf

73 ms

t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf

t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf

74 ms

bmC0pGMXrhphrZJmniIZpZ0EAVxt0G0biEntp43Qt6E.ttf

bmC0pGMXrhphrZJmniIZpZ0EAVxt0G0biEntp43Qt6E.ttf

74 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

73 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

72 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

91 ms

Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf

Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf

93 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

93 ms

mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf

mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf

91 ms

evC1haE-MsorTl_A7_uSGaCWcynf_cDxXwCLxiixG1c.ttf

evC1haE-MsorTl_A7_uSGaCWcynf_cDxXwCLxiixG1c.ttf

102 ms

2hig-tnMw8lXZsjwuh-9ow.ttf

2hig-tnMw8lXZsjwuh-9ow.ttf

92 ms

translate_24dp.png

translate_24dp.png

49 ms

l

l

75 ms

cleardot.gif

cleardot.gif

197 ms

MediaFramework.js

MediaFramework.js

45 ms

te_ctrl3.gif

te_ctrl3.gif

72 ms

ButtonRightBkg.png

ButtonRightBkg.png

38 ms

ButtonLeftBkg.png

ButtonLeftBkg.png

40 ms

Print.css

Print.css

51 ms

piwik.js

piwik.js

146 ms

Document

Document

235 ms

Accessibility Review

accessfayetteville.org accessibility score

80

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-hidden="true"] elements contain focusable descendents

High

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

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

accessfayetteville.org SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

accessfayetteville.org

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