8.3 sec in total
44 ms
8.1 sec
201 ms
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.comWe analyzed Parkannapolis.com page load time and found that the first response time was 44 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
parkannapolis.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value14.8 s
0/100
25%
Value16.0 s
0/100
10%
Value3,400 ms
2/100
30%
Value0.006
100/100
15%
Value22.5 s
1/100
10%
44 ms
112 ms
413 ms
5555 ms
114 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Parkannapolis.com, 78% (115 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 (5.6 sec) relates to the external source Annapolisparking.com.
Page size can be reduced by 192.7 kB (11%)
1.7 MB
1.5 MB
In fact, the total size of Parkannapolis.com main page is 1.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 180.2 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 180.2 kB or 84% of the original size.
Potential reduce by 3.7 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.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 7.4 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.
Number of requests can be reduced by 107 (82%)
130
23
The browser has sent 130 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 60 to 1 for JavaScripts and from 43 to 1 for CSS and as a result speed up the page load time.
parkannapolis.com
44 ms
annapolisparking.com
112 ms
annapolisparking.com
413 ms
www.annapolisparking.com
5555 ms
wp-emoji-release.min.js
114 ms
remodal.css
50 ms
remodal-default-theme.css
52 ms
marker-library-dialog.css
46 ms
bdt-uikit.css
57 ms
ep-helper.css
70 ms
style.min.css
85 ms
cleantalk-public.min.css
83 ms
style-frontend-pro.1.20.2.css
74 ms
wpda_public.css
92 ms
header-footer-elementor.css
113 ms
frontend-legacy.min.css
93 ms
frontend-lite.min.css
96 ms
post-46521.css
106 ms
frontend.min.css
127 ms
frontend-lite.min.css
116 ms
global.css
122 ms
post-3815.css
239 ms
frontend.css
138 ms
post-46530.css
145 ms
post-46532.css
149 ms
style.css
152 ms
font-awesome.css
48 ms
font-awesome-corp.css
153 ms
font-awesome-ext.css
156 ms
font-awesome-social.css
161 ms
css
59 ms
js
111 ms
jquery.min.js
153 ms
jquery-migrate.min.js
161 ms
jquery.dd.js
157 ms
geolocate.js
165 ms
infobox.js
168 ms
jquery.ui.map.js
162 ms
remodal.min.js
169 ms
apbct-public-bundle.min.js
166 ms
underscore-before.js
172 ms
underscore.min.js
170 ms
widget-posts.min.css
138 ms
ol.css
137 ms
open-layers.css
138 ms
underscore-after.js
119 ms
all.css
172 ms
fa-4to5.css
101 ms
common.css
110 ms
datatables.css
97 ms
default.css
96 ms
owl.carousel.min.css
95 ms
owl.theme.default.min.css
90 ms
carousel_sky.css
95 ms
featherlight.min.css
97 ms
dataTables.responsive.css
82 ms
wpgmaps-admin.css
108 ms
wpgmza_style_pro.css
100 ms
legacy-modern.css
82 ms
animations.min.css
76 ms
backbone.min.js
73 ms
api-request.min.js
67 ms
wp-api.min.js
79 ms
wpda_rest_api.js
76 ms
wpgmza_data.js
78 ms
front-end-free.1.20.2.js
67 ms
navigation.js
243 ms
frontend.js
314 ms
imagesloaded.min.js
314 ms
dummy.js
320 ms
ol.js
315 ms
datatables.min.js
666 ms
dataTables.responsive.js
307 ms
jquery-cookie.js
305 ms
pep.js
305 ms
text.js
304 ms
pako_deflate.min.js
303 ms
wp-google-maps-pro.min.js
307 ms
kdTree-min.js
304 ms
cheap-ruler.js
301 ms
wp-google-maps-gold.min.js
304 ms
owl.carousel.js
302 ms
featherlight.min.js
306 ms
polyline.js
301 ms
core.min.js
302 ms
mouse.min.js
302 ms
sortable.min.js
300 ms
bdt-uikit.min.js
304 ms
webpack.runtime.min.js
301 ms
frontend-modules.min.js
293 ms
waypoints.min.js
291 ms
frontend.min.js
293 ms
helper.min.js
281 ms
webpack-pro.runtime.min.js
281 ms
regenerator-runtime.min.js
282 ms
wp-polyfill.min.js
290 ms
hooks.min.js
287 ms
i18n.min.js
610 ms
frontend.min.js
605 ms
elements-handlers.min.js
275 ms
jquery.sticky.min.js
604 ms
gen_204
213 ms
gtm.js
755 ms
_Incapsula_Resource
671 ms
1485 ms
anapolis-logo.png
596 ms
onstreet-changes05102022-0.jpg
596 ms
directions_car.png
594 ms
directions_walking.png
594 ms
directions_transit.png
1026 ms
directions_bike.png
1025 ms
footer-annapolis.jpg
1157 ms
annapolis-logo-footer.png
1024 ms
spplus-municipal-footer-logo-dark-bg.png
1022 ms
DroidSans.ttf
1239 ms
DroidSans-Bold.ttf
1347 ms
6aez4K2oVqwIvtU2Gg.ttf
576 ms
6ae84K2oVqwItm4TCpAy3w.ttf
675 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
1008 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
1009 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
1055 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
1101 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
1100 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
1054 ms
fa-solid-900.woff
693 ms
fa-regular-400.woff
828 ms
42markers.xml
178 ms
common.js
127 ms
util.js
175 ms
controls.js
174 ms
places_impl.js
206 ms
_Incapsula_Resource
106 ms
6262.png
281 ms
6263.png
280 ms
6262.png
280 ms
6261.png
386 ms
6263.png
417 ms
6263.png
413 ms
6261.png
416 ms
6262.png
384 ms
6261.png
415 ms
spotlight-poi2.png
282 ms
pre-purchase.png
368 ms
powered-by-google-on-white3.png
236 ms
autocomplete-icons.png
224 ms
annapolis-pin.png
67 ms
pre-purchase.png
54 ms
parkannapolis.com accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
parkannapolis.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
parkannapolis.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: