Tools & Wizards About Us
norfolk.gov screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

norfolk.gov

City of Norfolk, Virginia - Official Website | Official Website

Page Load Speed

2.5 sec in total

First Response

94 ms

Resources Loaded

1.9 sec

Page Rendered

465 ms

norfolk.gov screenshot

About Website

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

The official City of Norfolk website.

Visit norfolk.gov

Key Findings

We analyzed Norfolk.gov page load time and found that the first response time was 94 ms and then it took 2.4 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

norfolk.gov performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value40.0 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value2,000 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.157

74/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

norfolk.gov

94 ms

www.norfolk.gov

94 ms

www.norfolk.gov

963 ms

gtm.js

83 ms

gtm.js

104 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 71% of them (44 requests) were addressed to the original Norfolk.gov, 6% (4 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (963 ms) belongs to the original domain Norfolk.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.9 kB (11%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 128.4 kB

  • Original 154.1 kB
  • After minification 145.6 kB
  • After compression 25.8 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 128.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

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

JavaScript Optimization

-8%

Potential reduce by 12.6 kB

  • Original 151.2 kB
  • After minification 151.1 kB
  • After compression 138.6 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

-21%

Potential reduce by 1.5 kB

  • Original 7.2 kB
  • After minification 7.2 kB
  • After compression 5.7 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. Norfolk.gov needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (69%)

Requests Now

59

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

norfolk.gov

norfolk.gov

94 ms

www.norfolk.gov

www.norfolk.gov

94 ms

www.norfolk.gov

www.norfolk.gov

963 ms

gtm.js

gtm.js

83 ms

gtm.js

gtm.js

104 ms

antiforgery

antiforgery

104 ms

fbevents.js

fbevents.js

32 ms

monsido-script.js

monsido-script.js

104 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

156 ms

jQuery-migrate-1.4.1.js

jQuery-migrate-1.4.1.js

208 ms

-1542169068.css

-1542169068.css

281 ms

100450599.css

100450599.css

355 ms

248816995.js

248816995.js

377 ms

ai.0.js

ai.0.js

19 ms

jquery.ui.autocomplete.min.js

jquery.ui.autocomplete.min.js

278 ms

Search.js

Search.js

278 ms

jquery-ui.css

jquery-ui.css

291 ms

Carousel.jquery.js

Carousel.jquery.js

221 ms

Easing.1.3.jquery.js

Easing.1.3.jquery.js

220 ms

Calendar.js

Calendar.js

220 ms

miniCalendar.js

miniCalendar.js

279 ms

jquery.urlToLink.min.js

jquery.urlToLink.min.js

279 ms

745732998.css

745732998.css

279 ms

APIClient.js

APIClient.js

310 ms

Moment.min.js

Moment.min.js

310 ms

SplashModalRender.js

SplashModalRender.js

311 ms

1342445881.js

1342445881.js

447 ms

monsido.js

monsido.js

98 ms

bot.js

bot.js

124 ms

analytics.js

analytics.js

60 ms

js

js

59 ms

collect

collect

14 ms

js

js

86 ms

Document

Document

50 ms

Document

Document

51 ms

Document

Document

214 ms

Document

Document

53 ms

Document

Document

50 ms

Document

Document

97 ms

Document

Document

95 ms

Document

Document

92 ms

Document

Document

300 ms

Document

Document

140 ms

Document

Document

140 ms

Document

Document

143 ms

Document

Document

162 ms

Document

Document

134 ms

Document

Document

162 ms

Document

Document

120 ms

Document

Document

161 ms

Document

Document

245 ms

Document

Document

163 ms

Document

Document

173 ms

Document

Document

157 ms

siteanalyze_1303276.js

siteanalyze_1303276.js

53 ms

ga.js

ga.js

33 ms

__utm.gif

__utm.gif

19 ms

image.aspx

image.aspx

16 ms

Print.css

Print.css

43 ms

tracking.monsido.com

tracking.monsido.com

86 ms

heatmaps.js

heatmaps.js

73 ms

dqwM4mF3GJsxuLtKx4qEkg.json

dqwM4mF3GJsxuLtKx4qEkg.json

4 ms

Accessibility Review

norfolk.gov accessibility score

74

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.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

Best Practices

norfolk.gov 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

Missing source maps for large first-party JavaScript

SEO Factors

norfolk.gov SEO score

83

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

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

High

Tap targets are not sized appropriately

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 Norfolk.gov 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 Norfolk.gov 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

norfolk.gov

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