7 sec in total
241 ms
5.9 sec
890 ms
Welcome to fwd-motion.org homepage info - get ready to check Fwd Motion best content right away, or after learning these important things about fwd-motion.org
Forward Motion is a bucket listing organization based in San Francisco, California. We help connect people through meaningful experiences.
Visit fwd-motion.orgWe analyzed Fwd-motion.org page load time and found that the first response time was 241 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fwd-motion.org performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value16.1 s
0/100
25%
Value15.0 s
1/100
10%
Value3,100 ms
2/100
30%
Value0.011
100/100
15%
Value16.1 s
6/100
10%
241 ms
3591 ms
156 ms
240 ms
376 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 61% of them (66 requests) were addressed to the original Fwd-motion.org, 18% (20 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Fwd-motion.org.
Page size can be reduced by 917.3 kB (37%)
2.5 MB
1.5 MB
In fact, the total size of Fwd-motion.org main page is 2.5 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 79.7 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 79.7 kB or 82% of the original size.
Potential reduce by 3.8 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. Fwd Motion images are well optimized though.
Potential reduce by 185.5 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 185.5 kB or 41% of the original size.
Potential reduce by 648.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. Fwd-motion.org needs all CSS files to be minified and compressed as it can save up to 648.4 kB or 78% of the original size.
Number of requests can be reduced by 67 (69%)
97
30
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fwd Motion. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
fwd-motion.org
241 ms
www.fwd-motion.org
3591 ms
cf7ic-style.css
156 ms
flick.css
240 ms
www.fwd-motion.org
376 ms
sbi-styles.min.css
316 ms
style.min.css
398 ms
styles.css
163 ms
portfolio.css
391 ms
style.css
325 ms
font-awesome.min.css
400 ms
grid-system.css
479 ms
style.css
717 ms
magnific.css
456 ms
css
32 ms
responsive.css
472 ms
select2.css
476 ms
ascend.css
480 ms
js_composer.min.css
689 ms
salient-dynamic-styles.css
553 ms
css
23 ms
jquery.min.js
563 ms
jquery-migrate.min.js
564 ms
scrollTo.js
562 ms
jquery.form.min.js
635 ms
mailchimp.js
635 ms
core.min.js
638 ms
datepicker.js
640 ms
index.js
777 ms
index.js
777 ms
imagesLoaded.min.js
778 ms
isotope.min.js
778 ms
salient-portfolio.js
779 ms
touchswipe.min.js
823 ms
caroufredsel.min.js
823 ms
salient-social.js
822 ms
jquery.easing.js
822 ms
jquery.mousewheel.js
823 ms
priority.js
823 ms
transit.js
893 ms
waypoints.js
811 ms
hoverintent.js
802 ms
magnific.js
729 ms
superfish.js
647 ms
init.js
781 ms
jquery.flexslider-min.js
694 ms
nectar-blog.js
672 ms
select2.min.js
667 ms
js_composer_front.min.js
667 ms
sbi-scripts.min.js
612 ms
analytics.js
116 ms
sbi-sprite.png
435 ms
forward-motion-logo-sm.png
435 ms
ball-pit-the-great-northern.jpg
435 ms
Ball-Pit-Dance-Party-Monarch-San-Francisco-59-600x403.jpg
435 ms
ball-pit-bar-600x403.jpg
448 ms
massive-messy-twister-600x403.jpg
658 ms
531770_414450551999624_763473516_n-600x403.jpg
660 ms
Giant-Slip-N-Slide-Forward-Motion-San-Diego-2-600x403.jpg
663 ms
Habitat-for-Humanity-Forward-Motion-1-600x403.jpg
661 ms
Hang-Glide-Forward-Motion-San-Francisco-5-600x403.jpg
662 ms
Bucket-List-Sunset-Kayak-San-Diego-02-600x403.jpg
663 ms
San-Francisco-SPCA-Ballpit-05-600x403.jpg
813 ms
ball-pit-bar-forward-motion-dance-party-600x403.jpg
814 ms
page.php
273 ms
page.php
795 ms
page.php
729 ms
blur.png
165 ms
home-header.jpg
880 ms
transparent.png
757 ms
w8gdH283Tvk__Lua32TysjIfp8uK.ttf
35 ms
5aU19_a8oxmIfNJdERySiA.ttf
37 ms
5aU19_a8oxmIfMJaERySiA.ttf
37 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
37 ms
icomoon.woff
708 ms
fontawesome-webfont.svg
831 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
71 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
74 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
127 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
128 ms
collect
43 ms
js
244 ms
LWbfNRBVLRg.css
22 ms
05nML2Cq08W.css
26 ms
XF5yXZbO9W2.css
31 ms
sGcGGNWA3Bv.js
107 ms
BECqV_OB-Tv.js
51 ms
teTZ2tZqwkq.js
30 ms
xNa_5SPtPNu.js
104 ms
p55HfXW__mM.js
106 ms
e7Tp58KLYmo.js
142 ms
q4SZVAjzsaO.js
104 ms
cMurRu-0m07.js
149 ms
sDCevwhL5Lw.js
165 ms
Le1VPU8p2Ny.js
163 ms
7FeuJQyTR-0.js
171 ms
Z3-ZOLt7ygu.js
165 ms
HzxD9aAXSyD.js
164 ms
309349120_400597042240514_4332999508099482195_n.jpg
603 ms
ZX-pzGZzr7q.js
565 ms
kCwDvxe1QsQ.js
563 ms
3wPO0nt3KaS.js
565 ms
307665293_400597038907181_271016378915863818_n.jpg
566 ms
UXtr_j2Fwe-.png
564 ms
307319543_417269860546260_1494290935213494305_n.jpg
428 ms
309000737_417269857212927_2863780523705892707_n.jpg
378 ms
326424834_1428772511194091_6369043473316952408_n.jpg
316 ms
326798402_1880537728947306_4825404974793446315_n.jpg
286 ms
fontawesome-webfont.woff
165 ms
fwd-motion.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fwd-motion.org 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fwd-motion.org 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
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 Fwd-motion.org 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 Fwd-motion.org 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.
fwd-motion.org
Open Graph data is detected on the main page of Fwd Motion. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: