9.6 sec in total
645 ms
7.3 sec
1.7 sec
Welcome to forecast.ly homepage info - get ready to check Forecast best content for United States right away, or after learning these important things about forecast.ly
This domain may be for sale!
Visit forecast.lyWe analyzed Forecast.ly page load time and found that the first response time was 645 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
forecast.ly performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value6.1 s
12/100
25%
Value9.8 s
10/100
10%
Value2,220 ms
6/100
30%
Value0.077
95/100
15%
Value21.4 s
1/100
10%
645 ms
378 ms
801 ms
361 ms
124 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 35% of them (62 requests) were addressed to the original Forecast.ly, 23% (41 requests) were made to Maps.google.com and 4% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Api.segment.io.
Page size can be reduced by 2.4 MB (53%)
4.5 MB
2.1 MB
In fact, the total size of Forecast.ly main page is 4.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. 80% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 137.1 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 137.1 kB or 85% of the original size.
Potential reduce by 240.4 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. Obviously, Forecast needs image optimization as it can save up to 240.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.4 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.4 MB or 72% of the original size.
Potential reduce by 606.1 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. Forecast.ly needs all CSS files to be minified and compressed as it can save up to 606.1 kB or 87% of the original size.
Number of requests can be reduced by 95 (61%)
157
62
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forecast. 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 13 to 1 for CSS and as a result speed up the page load time.
forecast.ly
645 ms
www.forecast.ly
378 ms
www.forecast.ly
801 ms
3117760382.js
361 ms
css
124 ms
css
140 ms
css
159 ms
styles.css
53 ms
rgs.css
107 ms
font-awesome.min.css
158 ms
style.css
157 ms
responsive.css
180 ms
ascend.css
153 ms
wpgform.css
195 ms
js_composer.css
234 ms
jquery.js
239 ms
jquery-migrate.min.js
211 ms
modernizr.js
238 ms
land.js
249 ms
tractionboard.min.js
494 ms
trackingCode.js
121 ms
core.min.js
237 ms
widget.min.js
310 ms
position.min.js
313 ms
menu.min.js
259 ms
autocomplete.min.js
268 ms
wpss-search-suggest.js
270 ms
jquery.form.min.js
275 ms
scripts.js
300 ms
respond.js
311 ms
sticky.js
325 ms
prettyPhoto.js
324 ms
isotope.min.js
475 ms
superfish.js
479 ms
init.js
494 ms
nectar-slider.js
834 ms
comment-reply.min.js
473 ms
wp-embed.min.js
472 ms
js_composer_front.js
474 ms
map.js
476 ms
count.js
476 ms
wp-emoji-release.min.js
389 ms
style.css
92 ms
analytics.min.js
427 ms
site-logo.png
299 ms
right_inv.jpg
836 ms
cart-icon.png
299 ms
down-graph-icon.png
370 ms
calc-icon.png
477 ms
left_dash.jpg
473 ms
adj-icon.png
371 ms
glasses-icon.png
371 ms
dlr-icon.png
379 ms
top_view.png
640 ms
thin_imac_dark.jpg
476 ms
mbp_mouse.jpg
638 ms
OpenSans-Regular-webfont.woff
323 ms
OpenSans-Light-webfont.woff
484 ms
OpenSans-Semibold-webfont.woff
485 ms
OpenSansBold-webfont.woff
487 ms
LKf8nhXsWg5ybwEGXk8UBQ.woff
73 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
141 ms
Lovelo_Black.woff
596 ms
icomoon.woff
596 ms
QHIOz1iKF3bIEzRdDFaf5dgliI79_bmRXH6crmREtCo.woff
141 ms
linecons.ttf
2073 ms
fontawesome-webfont.svg
676 ms
steadysets.ttf
677 ms
land.gif
152 ms
trackingCode.html
113 ms
dpx
339 ms
dpx
338 ms
p
2255 ms
t
2247 ms
conversion_async.js
1794 ms
track.js
1579 ms
fbevents.js
1820 ms
analytics.js
1827 ms
heap-3321802017.js
1895 ms
mlo4a2v8
1941 ms
mixpanel-2-latest.min.js
1992 ms
raven.min.js
1933 ms
w.js
1994 ms
8877657.js
1884 ms
tracker.js
1883 ms
gtm.js
1929 ms
558a9e3bed0565506200016c.js
1990 ms
count.js
1703 ms
www.forecast.ly
1273 ms
dashboard_dark.jpg
669 ms
js
684 ms
ajax-loader.gif
391 ms
diagonal_line.png
314 ms
fontawesome-webfont.woff
435 ms
463 ms
638 ms
linkid.js
170 ms
visit
316 ms
h
529 ms
h
526 ms
intercom.bcfdf787.js
531 ms
dashboard_dark.jpg
1527 ms
623 ms
638 ms
collect
107 ms
collect
630 ms
895 ms
collect
210 ms
collect
330 ms
collect
844 ms
pv
595 ms
common.js
95 ms
map.js
168 ms
497 ms
track
219 ms
util.js
261 ms
onion.js
261 ms
openhand_8_8.cur
589 ms
ViewportInfoService.GetViewportInfo
1024 ms
stats.js
276 ms
controls.js
266 ms
echo.515e8809.js
124 ms
ping
547 ms
tagjs
196 ms
css
207 ms
transparent.png
223 ms
google4.png
202 ms
mapcnt6.png
192 ms
sv5.png
208 ms
507 ms
tmapctrl4.png
196 ms
google_white5.png
216 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
71 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
66 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
282 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
281 ms
Pug
566 ms
adsct
621 ms
pixel
528 ms
ncm
281 ms
cb
296 ms
vt
104 ms
vt
59 ms
vt
55 ms
vt
113 ms
vt
144 ms
vt
144 ms
vt
111 ms
vt
114 ms
vt
114 ms
vt
114 ms
vt
141 ms
vt
142 ms
vt
140 ms
vt
140 ms
vt
158 ms
vt
158 ms
vt
156 ms
vt
206 ms
vt
156 ms
vt
153 ms
vt
170 ms
vt
166 ms
vt
166 ms
vt
169 ms
vt
169 ms
vt
178 ms
vt
187 ms
vt
186 ms
vt
187 ms
vt
187 ms
vt
194 ms
vt
219 ms
vt
195 ms
vt
243 ms
sd
47 ms
tap.php
60 ms
cb
52 ms
cb
9 ms
forecast.ly 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.
forecast.ly 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
forecast.ly 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
Page is blocked from indexing
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forecast.ly 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 Forecast.ly 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.
forecast.ly
Open Graph data is detected on the main page of Forecast. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: