93.5 sec in total
203 ms
79.5 sec
13.8 sec
Click here to check amazing Hometownannapolis content. Otherwise, check out these important facts you probably never knew about hometownannapolis.com
Annapolis and Anne Arundel County real estate listings and news from Capital Gazette
Visit hometownannapolis.comWe analyzed Hometownannapolis.com page load time and found that the first response time was 203 ms and then it took 93.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
hometownannapolis.com performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value18.3 s
0/100
25%
Value39.9 s
0/100
10%
Value53,310 ms
0/100
30%
Value0.303
39/100
15%
Value84.0 s
0/100
10%
203 ms
3223 ms
644 ms
1827 ms
1826 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hometownannapolis.com, 10% (15 requests) were made to S0.2mdn.net and 9% (14 requests) were made to T.teads.tv. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Sync.adaptv.advertising.com.
Page size can be reduced by 2.5 MB (63%)
4.0 MB
1.5 MB
In fact, the total size of Hometownannapolis.com main page is 4.0 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. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 238.6 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 238.6 kB or 80% of the original size.
Potential reduce by 4.5 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. Hometownannapolis images are well optimized though.
Potential reduce by 1.7 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.7 MB or 65% of the original size.
Potential reduce by 639.0 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. Hometownannapolis.com needs all CSS files to be minified and compressed as it can save up to 639.0 kB or 88% of the original size.
Number of requests can be reduced by 87 (66%)
132
45
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hometownannapolis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and as a result speed up the page load time.
hometownannapolis.com
203 ms
3223 ms
gpt.js
644 ms
lib.1q2w3_f16b5c4e2d8bca779a766d6cdeb42433.min.js
1827 ms
main.1q2w3_d8b30f2574e8e7dfda78386e4a837a1c.min.js
1826 ms
cgngux.min.js
1815 ms
cgngux.min.js
1817 ms
htw-baltimore-sun.js
625 ms
Bootstrap.js
1705 ms
modules.1q2w3_cd8a468be936e9471270c366af3dfba4.min.css
598 ms
pubads_impl_147.js
6357 ms
publishertag.js
5987 ms
fastlane.json
5651 ms
fastlane.json
5649 ms
fastlane.json
5567 ms
fastlane.json
5475 ms
cygnus
5333 ms
JucOy8YK.js
3031 ms
1250x703
1794 ms
cgngux-reaction-1q2w3-4325750788377395048.min.js
628 ms
200x113
791 ms
200x113
592 ms
200x113
517 ms
200x113
517 ms
200x113
591 ms
serverComponent.php
514 ms
arj
552 ms
pd
490 ms
cfcm.ashx
338 ms
openx
147 ms
pixel
232 ms
sd
257 ms
openx
256 ms
pixel
547 ms
sd
4377 ms
sd
3937 ms
sd
3927 ms
sd
3926 ms
ads
1661 ms
met-close-1q2w3-f5555c767886388f3efd727f95951e54.png
1184 ms
controltag.js.1c86c30cac854ccdacab6e3099f5b9ee
561 ms
container.html
980 ms
analytics.js
1963 ms
chartbeat.js
1615 ms
ads
1171 ms
ads
5653 ms
ads
6283 ms
ads
6472 ms
ads
5643 ms
headerstats
5280 ms
proxy.3d2100fd7107262ecb55ce6847f01fa5.html
2310 ms
ping
2016 ms
tag
2014 ms
osd.js
1285 ms
container.html
1072 ms
gen_204
2272 ms
ad
3381 ms
m_window_focus_non_hydra.js
2637 ms
osd_listener.js
2855 ms
r2
2013 ms
teads-format.min.js
1748 ms
7476.js
1339 ms
gen_204
741 ms
ad
1401 ms
sync
648 ms
sync
557 ms
437135_-_Soleil_Laurel_Canyon_-_Walton_Street_-_Banner_Ad___728x90_.jpg
5477 ms
abg.js
1054 ms
lidar.js
4827 ms
d5qAyLYU.js
4898 ms
266632-2.js
5363 ms
266632-15.js
5345 ms
express_html_inpage_rendering_lib_200_183.js
4426 ms
pixel
3568 ms
optout_check
3867 ms
get
3251 ms
pixel
2273 ms
pixel
2273 ms
2.jpg
9403 ms
15.png
9297 ms
pixel
861 ms
cookie_push.html
934 ms
pixel
4900 ms
pixel
4899 ms
9im3l02I.html
732 ms
track
8427 ms
iframe
5374 ms
ad
2363 ms
12593 ms
user-registering
12594 ms
track
7395 ms
getdata.xgi
5833 ms
getdata.xgi
6013 ms
p
5301 ms
ad
4678 ms
track
6522 ms
track
6521 ms
track
6968 ms
track
6894 ms
track
6893 ms
T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js
6195 ms
redirect
4596 ms
index.html
4501 ms
moatad.js
5679 ms
teads-format.css
3245 ms
4e4c28a3-2874-4ecb-a8d2-7b764b5c8179
3032 ms
pixel
4748 ms
generic
16073 ms
sync
20455 ms
20454 ms
pixel
4596 ms
pixel
3866 ms
LeVO5Tt6
10739 ms
um
18969 ms
pixel
9825 ms
pixel.gif
11064 ms
um
17887 ms
player-sprite.svg
9078 ms
moatvideo.js
8854 ms
track
8730 ms
300.meta
7161 ms
p
6758 ms
track
5678 ms
track
5744 ms
track
5303 ms
track
5668 ms
segments_to_partner.js
16027 ms
n.js
15348 ms
n.js
12662 ms
um
9199 ms
300.tv
6136 ms
44858
12948 ms
activeview
7332 ms
activeview
7281 ms
um
10587 ms
reguslogo_wht.png
6990 ms
Asset-14x.png
6913 ms
Asset-34x.png
9199 ms
Asset-44x.png
9239 ms
Asset-134x.png
9164 ms
Asset-64x.png
9295 ms
Asset-74x.png
9237 ms
Asset-114x.png
9238 ms
Asset-124x.png
9291 ms
Asset-15.png
9800 ms
Asset-18.png
9799 ms
Asset-94x.png
10964 ms
activity;src=4487534;pid=150420053;aid=321158248;ko=0;cid=81550586;rid=81429986;rv=1;met=1;×tamp=1504628979754;eid1=2;ecn1=1;etm1=20;eid2=871060;ecn2=1;etm2=0;
11732 ms
ping
5078 ms
pixel.gif
8835 ms
track
3327 ms
activity;src=4487534;pid=150420053;aid=321158248;ko=0;cid=81550586;rid=81429986;rv=1;met=1;×tamp=1504628985724;eid1=2;ecn1=0;etm1=6;
4982 ms
track
2927 ms
pixel.gif
3966 ms
hometownannapolis.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
hometownannapolis.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
hometownannapolis.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
Image elements do not have [alt] attributes
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hometownannapolis.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Hometownannapolis.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.
hometownannapolis.com
Open Graph description is not detected on the main page of Hometownannapolis. 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: