Tools & Wizards About Us
parkannapolis.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

parkannapolis.com

The Official Annapolis Parking Guide | City of Annapolis, Maryland (MD) Parking Guide

Page Load Speed

21.9 sec in total

First Response

16 ms

Resources Loaded

21.6 sec

Page Rendered

246 ms

parkannapolis.com screenshot

About Website

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

Welcome to the official parking guide for Annapolis, MD. Find the best parking locations, garages, destinations and more for residents and visitors.

Visit parkannapolis.com

Key Findings

We analyzed Parkannapolis.com page load time and found that the first response time was 16 ms and then it took 21.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

parkannapolis.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

parkannapolis.com

16 ms

annapolisparking.com

678 ms

remodal.css

24 ms

remodal-default-theme.css

30 ms

marker-library-dialog.css

31 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Parkannapolis.com, 83% (125 requests) were made to Annapolisparking.com and 5% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source .

Page Optimization Overview & Recommendations

Page size can be reduced by 227.6 kB (9%)

Content Size

2.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Parkannapolis.com main page is 2.4 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 176.8 kB

  • Original 214.1 kB
  • After minification 209.9 kB
  • After compression 37.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 176.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 674 B

  • Original 980.7 kB
  • After minification 980.1 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. Park Annapolis images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 39.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 1.1 MB

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

-7%

Potential reduce by 10.7 kB

  • Original 163.5 kB
  • After minification 163.4 kB
  • After compression 152.8 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. Parkannapolis.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 120 (90%)

Requests Now

134

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

parkannapolis.com

parkannapolis.com

16 ms

annapolisparking.com

annapolisparking.com

678 ms

remodal.css

remodal.css

24 ms

remodal-default-theme.css

remodal-default-theme.css

30 ms

marker-library-dialog.css

marker-library-dialog.css

31 ms

frontend.css

frontend.css

30 ms

bdt-uikit.css

bdt-uikit.css

38 ms

ep-helper.css

ep-helper.css

43 ms

style-frontend-pro.css

style-frontend-pro.css

64 ms

spwidget_styles.css

spwidget_styles.css

50 ms

jquery.dataTables.min.css

jquery.dataTables.min.css

54 ms

responsive.dataTables.min.css

responsive.dataTables.min.css

55 ms

icon

icon

81 ms

css

css

101 ms

wickedpicker.css

wickedpicker.css

55 ms

mapbox-gl.css

mapbox-gl.css

60 ms

wpda_public.css

wpda_public.css

55 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

62 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

62 ms

widget-base.min.css

widget-base.min.css

79 ms

header-footer-elementor.css

header-footer-elementor.css

71 ms

frontend-lite.min.css

frontend-lite.min.css

73 ms

swiper.min.css

swiper.min.css

89 ms

post-46521.css

post-46521.css

90 ms

frontend.min.css

frontend.min.css

82 ms

frontend-lite.min.css

frontend-lite.min.css

89 ms

post-3815.css

post-3815.css

94 ms

post-46530.css

post-46530.css

89 ms

post-46532.css

post-46532.css

92 ms

style.css

style.css

91 ms

font-awesome.css

font-awesome.css

80 ms

font-awesome-corp.css

font-awesome-corp.css

96 ms

font-awesome-ext.css

font-awesome-ext.css

95 ms

font-awesome-social.css

font-awesome-social.css

96 ms

jquery-ui.css

jquery-ui.css

63 ms

css

css

112 ms

js

js

130 ms

jquery.min.js

jquery.min.js

95 ms

jquery-migrate.min.js

jquery-migrate.min.js

94 ms

jquery.dd.js

jquery.dd.js

98 ms

geolocate.js

geolocate.js

99 ms

infobox.js

infobox.js

97 ms

jquery.ui.map.js

jquery.ui.map.js

103 ms

remodal.min.js

remodal.min.js

101 ms

mapbox-gl.js

mapbox-gl.js

89 ms

jquery-barcode.js

jquery-barcode.js

82 ms

widget-posts.min.css

widget-posts.min.css

20074 ms

all.css

all.css

75 ms

globalpayments.js

globalpayments.js

65 ms

libphonenumber-js.min.js

libphonenumber-js.min.js

76 ms

animations.min.css

animations.min.css

77 ms

ol.css

ol.css

75 ms

open-layers.css

open-layers.css

72 ms

f208fedfb8.js

f208fedfb8.js

93 ms

fa-4to5.css

fa-4to5.css

74 ms

common.css

common.css

65 ms

jquery.dataTables.min.css

jquery.dataTables.min.css

69 ms

default.css

default.css

58 ms

owl.carousel.min.css

owl.carousel.min.css

55 ms

owl.theme.default.min.css

owl.theme.default.min.css

54 ms

carousel_sky.css

carousel_sky.css

52 ms

featherlight.min.css

featherlight.min.css

59 ms

dataTables.responsive.css

dataTables.responsive.css

47 ms

wpgmaps-admin.css

wpgmaps-admin.css

46 ms

wpgmza_style_pro.css

wpgmza_style_pro.css

46 ms

legacy-modern.css

legacy-modern.css

41 ms

underscore-before.js

underscore-before.js

34 ms

underscore.min.js

underscore.min.js

41 ms

underscore-after.js

underscore-after.js

36 ms

backbone.min.js

backbone.min.js

23 ms

api-request.min.js

api-request.min.js

23 ms

wp-api.min.js

wp-api.min.js

29 ms

wpda_rest_api.js

wpda_rest_api.js

30 ms

wpgmza_data.js

wpgmza_data.js

29 ms

front-end-free.js

front-end-free.js

29 ms

core.min.js

core.min.js

30 ms

datepicker.min.js

datepicker.min.js

30 ms

moment.js

moment.js

27 ms

moment-timezone.js

moment-timezone.js

28 ms

moment-with-locales.min.js

moment-with-locales.min.js

31 ms

wickedpicker.js

wickedpicker.js

30 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

29 ms

dataTables.responsive.min.js

dataTables.responsive.min.js

28 ms

datetime-moment.js

datetime-moment.js

28 ms

spwidget_script.js

spwidget_script.js

104 ms

navigation.js

navigation.js

28 ms

controlgroup.min.js

controlgroup.min.js

26 ms

checkboxradio.min.js

checkboxradio.min.js

102 ms

button.min.js

button.min.js

28 ms

spinner.min.js

spinner.min.js

26 ms

jquery.sticky.min.js

jquery.sticky.min.js

100 ms

frontend.js

frontend.js

100 ms

imagesloaded.min.js

imagesloaded.min.js

100 ms

dummy.js

dummy.js

100 ms

ol.js

ol.js

107 ms

datatables.min.js

datatables.min.js

106 ms

dataTables.responsive.js

dataTables.responsive.js

100 ms

jquery-cookie.js

jquery-cookie.js

105 ms

pep.js

pep.js

102 ms

text.js

text.js

101 ms

pako_deflate.min.js

pako_deflate.min.js

103 ms

wp-google-maps-pro.min.js

wp-google-maps-pro.min.js

107 ms

kdTree-min.js

kdTree-min.js

104 ms

cheap-ruler.js

cheap-ruler.js

104 ms

wp-google-maps-gold.min.js

wp-google-maps-gold.min.js

98 ms

owl.carousel.js

owl.carousel.js

95 ms

featherlight.min.js

featherlight.min.js

95 ms

polyline.js

polyline.js

97 ms

mouse.min.js

mouse.min.js

96 ms

sortable.min.js

sortable.min.js

96 ms

bdt-uikit.min.js

bdt-uikit.min.js

96 ms

webpack.runtime.min.js

webpack.runtime.min.js

94 ms

frontend-modules.min.js

frontend-modules.min.js

96 ms

waypoints.min.js

waypoints.min.js

94 ms

frontend.min.js

frontend.min.js

93 ms

helper.min.js

helper.min.js

92 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

93 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

93 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

92 ms

wp-polyfill.min.js

wp-polyfill.min.js

93 ms

hooks.min.js

hooks.min.js

93 ms

i18n.min.js

i18n.min.js

91 ms

frontend.min.js

frontend.min.js

93 ms

elements-handlers.min.js

elements-handlers.min.js

68 ms

gtm.js

gtm.js

138 ms

hillman-reopening05192023.jpg

hillman-reopening05192023.jpg

98 ms

onstreet-changes05102022-0.jpg

onstreet-changes05102022-0.jpg

93 ms

_Incapsula_Resource

_Incapsula_Resource

30 ms

561 ms

anapolis-logo.png

anapolis-logo.png

20 ms

directions_car.png

directions_car.png

21 ms

directions_walking.png

directions_walking.png

21 ms

directions_transit.png

directions_transit.png

19 ms

directions_bike.png

directions_bike.png

24 ms

annapolis-logo-footer.png

annapolis-logo-footer.png

23 ms

spplus-metropolis-footer-white.png

spplus-metropolis-footer-white.png

21 ms

6ae84K2oVqwItm4TCpAy3w.ttf

6ae84K2oVqwItm4TCpAy3w.ttf

20 ms

6aez4K2oVqwIvtU2Gg.ttf

6aez4K2oVqwIvtU2Gg.ttf

37 ms

DroidSans-Bold.ttf

DroidSans-Bold.ttf

149 ms

DroidSans.ttf

DroidSans.ttf

167 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

55 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

73 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

73 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

74 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

75 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

74 ms

footer-annapolis.jpg

footer-annapolis.jpg

11 ms

fa-solid-900.woff

fa-solid-900.woff

123 ms

fa-regular-400.woff

fa-regular-400.woff

123 ms

_Incapsula_Resource

_Incapsula_Resource

101 ms

Accessibility Review

parkannapolis.com accessibility score

96

Accessibility Issues

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

parkannapolis.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

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

parkannapolis.com SEO score

97

Search Engine Optimization Advices

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

parkannapolis.com

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