2.2 sec in total
385 ms
1.7 sec
95 ms
Click here to check amazing Azavea Forms content for United States. Otherwise, check out these important facts you probably never knew about azavea.forms.fm
Visit azavea.forms.fmWe analyzed Azavea.forms.fm page load time and found that the first response time was 385 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
azavea.forms.fm performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value10.0 s
0/100
25%
Value3.5 s
89/100
10%
Value730 ms
40/100
30%
Value0.014
100/100
15%
Value10.0 s
26/100
10%
385 ms
551 ms
48 ms
276 ms
46 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 10% of them (3 requests) were addressed to the original Azavea.forms.fm, 31% (9 requests) were made to Use.typekit.net and 10% (3 requests) were made to D3bt6306j428ad.cloudfront.net. The less responsive or slowest element that took the longest time to load (551 ms) belongs to the original domain Azavea.forms.fm.
Page size can be reduced by 285.1 kB (61%)
468.4 kB
183.3 kB
In fact, the total size of Azavea.forms.fm main page is 468.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 355.9 kB which makes up the majority of the site volume.
Potential reduce by 9.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 9.2 kB or 56% of the original size.
Potential reduce by 5 B
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. Azavea Forms images are well optimized though.
Potential reduce by 197.2 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 197.2 kB or 55% of the original size.
Potential reduce by 78.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. Azavea.forms.fm needs all CSS files to be minified and compressed as it can save up to 78.7 kB or 82% of the original size.
Number of requests can be reduced by 8 (42%)
19
11
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Azavea Forms. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
azavea.forms.fm
385 ms
azavea.forms.fm
551 ms
respondent_view-dd2fb62bcb11db41d380a798d4ba298ab7a7a82bb3bfd29ef3859e1b2f3cc968.css
48 ms
colors.css
276 ms
jquery.min.js
46 ms
ckb1dps.js
134 ms
respondent_view-a9d6868a10ccc210735ba7ba352fbc85c3d7ebd7d7e87b43bdeb4df64012d8f4.js
58 ms
bugsnag-2.min.js
23 ms
azavea.forms.fm
115 ms
analytics.min.js
156 ms
thumb_azavea_RGB_72dpi_trans_175x50.gif
92 ms
analytics.js
64 ms
CJq1WmqMCMHZIPKlrvcDgjHE9ORplLhnTvnfL5yj95XffHhUggMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
35 ms
DAJmgZXofWq1ozXJjIn66Wt6RokT7I7AEEWOlHorlL6ff5-oggMdeMJ6Mk6g5Mmfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
72 ms
BVYI7YQGkoFgK2EdKAmZCfSW0f3mh0HNBM9bMy0ZeDjffOeUggMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
142 ms
VHmBs8fykoykTXVhzcdkbTmLnzCr0pGjIA1rkEKb6r6ff5eegsMdeMJ6Mk6g5M4fb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
169 ms
dobt-39c05ed2b1a33c6842e71816be0c46634a38ad8e7b0fdd95361576a4a41f2a0a.woff
9 ms
vG-3lHVkGTbBs1wfTwduMGVDoJEb7jzy97T-DMbWEmwffHEUggMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
183 ms
Zj96VbMWy_1-XDkgNA-KS58sYkVbKZLCWEafWEkemVqffOfUggMdeMJ6Mk6g5MNfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
171 ms
49gGe4yZBuu1JL16O_nPq3cMtNGh_xXjFp2mOAmzJAqffOHUggMdeMJ6Mk6g5gBfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
183 ms
collect
14 ms
mixpanel-2-latest.min.js
61 ms
collect
9 ms
collect
78 ms
p.gif
130 ms
37 ms
nr-885.min.js
48 ms
update.js
28 ms
o.png
9 ms
azavea.forms.fm accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
azavea.forms.fm 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
azavea.forms.fm SEO score
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
EN
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Azavea.forms.fm 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 Azavea.forms.fm main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
azavea.forms.fm
Open Graph description is not detected on the main page of Azavea Forms. 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: