foreca.com website information.

foreca.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for foreca.com domain:

ns2.viamedia.fi
ns.viamedia.fi
ns3.viamedia.fi

and probably website foreca.com is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.

According to Alexa traffic rank the highest website foreca.com position was 33850 (in the world). The lowest Alexa rank position was 112227. Now website foreca.com ranked in Alexa database as number 53105 (in the world).

Website foreca.com Desktop speed measurement score (86/100) is better than the results of 82.23% of other sites and shows that the page is performing great on desktop computers.

foreca.com Mobile usability score (68/100) is better than the results of 19.67% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of foreca.com (69/100) is better than the results of 74.36% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

Date	Rank	Change
Nov-18-2024	53,105	-123
Nov-17-2024	52,982	172
Nov-16-2024	53,154	-68
Nov-15-2024	53,086	-608
Nov-14-2024	52,478	190
Nov-13-2024	52,668	0
Nov-12-2024	52,668	0

foreca.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.

foreca.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.

Domain Name: FORECA.COM
Registry Domain ID: 40298567_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: http://www.cloudflare.com
Updated Date: 2023-10-09T19:57:46Z
Creation Date: 2000-11-08T15:38:16Z
Registry Expiry Date: 2024-11-08T15:38:16Z
Registrar: CloudFlare, Inc.
Registrar IANA ID: 1910
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: AMIT.NS.CLOUDFLARE.COM
Name Server: LIA.NS.CLOUDFLARE.COM
DNSSEC: signedDelegation
DNSSEC DS Data: 2371 13 2 8215B8A3D977B8F38B41604037D9DAB96BDBBB912AFFB8B8B0731D5E6CA5847D
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-09-09T12:15:32Z

foreca.com server information

Servers Location

IP Address
213.80.73.57
213.80.73.58

Country
Finland
Finland

Region
Uusimaa
Uusimaa

City
Espoo
Espoo

foreca.com desktop page speed rank

Last tested: 2019-12-02

Desktop Speed Good

86/100

foreca.com Desktop Speed Test Quick Summary

priority - 6 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://www.foreca.com/js/modernizr-2.7.1.min.js
https://www.foreca.com/js/consent-bundle.js?20180529

Optimize CSS Delivery of the following:

https://www.foreca.com/css/consent.min.css?20180716
https://www.foreca.com/css/combined-20191125.css

priority - 3 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://v1.addthisedge.com/live/boost/ra-5874deaad…_ate.track.config_resp (56 seconds)
https://s7.addthis.com/js/300/addthis_widget.js (10 minutes)
https://www.foreca.com/meteogram.php?loc_id=105128…ang=en&units=us&tf=12h (15 minutes)
https://www.foreca.com/ml (15 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://z.moatads.com/addthismoatframe568911941483/moatframe.js (10.3 hours)

priority - 3 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://foreca.com/
https://www.foreca.com/
https://www.foreca.com/United_States/New_York/New_York_City

priority - 2 Reduce server response time

In our test, your server responded in 0.36 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5.4KiB (45% reduction).

Compressing https://www.foreca.com/img/geode.png could save 2.7KiB (67% reduction).
Compressing https://img-b.foreca.net/i/e/trivia_hot-c.png?2 could save 2.5KiB (37% reduction).
Compressing https://www.foreca.com/img/foreca_logo_footer.png could save 318B (19% reduction).

foreca.com Desktop Resources

Total Resources	70
Number of Hosts	17
Static Resources	52
JavaScript Resources	20
CSS Resources	2

foreca.com Desktop Resource Breakdown

foreca.com mobile page speed rank

Last tested: 2019-12-02

Mobile Speed Medium

69/100

foreca.com Mobile Speed Test Quick Summary

priority - 24 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://www.foreca.com/js/modernizr-2.7.1.min.js
https://www.foreca.com/js/consent-bundle.js?20180529

Optimize CSS Delivery of the following:

https://www.foreca.com/css/consent.min.css?20180716
https://www.foreca.com/css/combined-20191125.css

priority - 10 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://foreca.com/
https://www.foreca.com/
https://www.foreca.com/United_States/New_York/New_York_City

priority - 8 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://pm.geniusmonkey.com/gm-08A48GG39.png (expiration not specified)
https://v1.addthisedge.com/live/boost/ra-5874deaad…_ate.track.config_resp (19 seconds)
https://s7.addthis.com/js/300/addthis_widget.js (10 minutes)
https://www.foreca.com/meteogram.php?loc_id=105128…ang=en&units=us&tf=12h (15 minutes)
https://www.foreca.com/ml (15 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://www.googletagservices.com/activeview/js/cu…ner.js?cache=r20110914 (50 minutes)
https://mts0.google.com/vt/data=HFkgQVgJtIh-lIgcfw…7iNt02UQUhj_bDI0nesodc (53.5 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://z.moatads.com/addthismoatframe568911941483/moatframe.js (3.7 hours)

priority - 3 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 25.1KiB (20% reduction).

Compressing https://tpc.googlesyndication.com/daca_images/simgad/9974934193829057795 could save 14KiB (18% reduction).
Compressing https://www.foreca.com/meteogram.php?loc_id=105128…ang=en&units=us&tf=12h could save 3.3KiB (12% reduction).
Compressing https://www.foreca.com/img/geode.png could save 2.7KiB (67% reduction).
Compressing https://img-b.foreca.net/i/e/trivia_hot-c.png?2 could save 2.5KiB (37% reduction).
Compressing https://tpc.googlesyndication.com/simgad/1519885705033054939 could save 2.3KiB (26% reduction).
Compressing https://www.foreca.com/img/foreca_logo_footer.png could save 318B (19% reduction).

priority - 2 Reduce server response time

In our test, your server responded in 0.36 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 541B (48% reduction).

Compressing https://us-u.openx.net/w/1.0/pd?ph=bbb82fae-1d27-4…u_D-EoHL_Bs7r-omORXCfw could save 541B (48% reduction).

foreca.com Mobile Resources

Total Resources	125
Number of Hosts	36
Static Resources	67
JavaScript Resources	25
CSS Resources	3

foreca.com Mobile Resource Breakdown

foreca.com mobile page usability

Last tested: 2019-12-02

Mobile Usability Medium

68/100

foreca.com Mobile Usability Test Quick Summary

priority - 39 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,200 CSS pixels wide, but the viewport is only 447 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="https://corpor….foreca.com/en">Company</a> falls outside the viewport.
The element <a href="https://corpor…om/en/products">Products & Services</a> falls outside the viewport.
The element <a href="https://corpor…com/en/contact">Contact</a> falls outside the viewport.
The element <div id="langtitle">Language…Українська</div> falls outside the viewport.
The element <p> falls outside the viewport.
The element <span>Follow</span> falls outside the viewport.
The element <path> falls outside the viewport.
The element <path> falls outside the viewport.
The element <div id="menuwrapper">Forecasts</div> falls outside the viewport.
The element <input id="autocomplete_input" type="text" name="q" class="colorInput ui-…complete-input"> falls outside the viewport.
The element <img src="//img-b.foreca…on_go-en.png?2"> falls outside the viewport.
The element <img src="/img/geode.png"> falls outside the viewport.
The element <strong>North America…New York City</strong> falls outside the viewport.
The element <strong>+</strong> falls outside the viewport.
The element <strong>°F</strong> falls outside the viewport.
The element <a href="/United_States…tf=12h&lang=en" class="letter-link">°C</a> falls outside the viewport.
The element <a href="/settings">Settings</a> falls outside the viewport.
The element <h1 class="entry-title">New York City, NY</h1> falls outside the viewport.
The element <a href="/United_States…ymb&zoom=state">NY</a> falls outside the viewport.
The element <a href="/United_States…b&zoom=country">US</a> falls outside the viewport.
The element <h2>Current conditions</h2> falls outside the viewport.
The element <select id="stations" name="station">Otis Air Natio…hurst/Nas, Nj.</select> falls outside the viewport.
The element <strong>32°</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>29.4 in</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>41°</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>93.3%</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>1 mi</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>07:01 am</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>04:29 pm</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <h2>3 day outlook</h2> falls outside the viewport.
The element <strong>Today</strong> falls outside the viewport.
The element <div class="symbol_50x50d…bol_d431_50x50"> falls outside the viewport.
The element <strong>38°</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>30°</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>Tomorrow</strong> falls outside the viewport.
The element <div class="symbol_50x50d…bol_d000_50x50"> falls outside the viewport.
The element <strong>40°</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>32°</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>Wednesday</strong> falls outside the viewport.
The element <div class="symbol_50x50d…bol_d300_50x50"> falls outside the viewport.
The element <strong>42°</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>33°</strong> falls outside the viewport.
The element <br> falls outside the viewport.
The element <strong>10 day forecast</strong> falls outside the viewport.
The element <img src="//img-b.foreca…i/e/arrow1.gif"> falls outside the viewport.
The element <h2>Detailed 5 day forecast</h2> falls outside the viewport.
The element <img src="/meteogram.php…nits=us&tf=12h"> falls outside the viewport.
The element <span>Updated at 02:…d at 02:40 pm.</span> falls outside the viewport.
The element <h3>Trivia</h3> falls outside the viewport.
The element <div>90°…avrongo, Ghana</div> falls outside the viewport.
The element <a href="/Russia/Oymyakon">Oymyakon</a> falls outside the viewport.
The element <strong>-49°</strong> falls outside the viewport.
The element <div class="symbol_29x20n…bol_n000_29x20"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <div>88° Tonj, Sudan</div> falls outside the viewport.
The element <a href="/Russia/Sarylakh">Sarylakh</a> falls outside the viewport.
The element <strong>-49°</strong> falls outside the viewport.
The element <div class="symbol_29x20n…bol_n000_29x20"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <div>81°…ay, Madagascar</div> falls outside the viewport.
The element <a href="/Russia/Nizhneyansk">Nizhneyansk</a> falls outside the viewport.
The element <strong>-45°</strong> falls outside the viewport.
The element <div class="symbol_29x20n…bol_n000_29x20"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <div>77°…Bentiu, Sudan</div> falls outside the viewport.
The element <a href="/Russia/Bodaybo">Bodaybo</a> falls outside the viewport.
The element <strong>-36°</strong> falls outside the viewport.
The element <div class="symbol_29x20n…bol_n400_29x20"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <div>68°…Malakal, Sudan</div> falls outside the viewport.
The element <a href="/Russia/Mamakan">Mamakan</a> falls outside the viewport.
The element <strong>-36°</strong> falls outside the viewport.
The element <div class="symbol_29x20n…bol_n400_29x20"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <iframe id="aswift_0" name="aswift_0"> falls outside the viewport.
The element <div class="clearb"></div> falls outside the viewport.
The element <iframe id="aswift_1" name="aswift_1"> falls outside the viewport.
The element <iframe id="aswift_2" name="aswift_2"> falls outside the viewport.
The element <h4>Observations</h4> falls outside the viewport.
The element <li>Radar</li> falls outside the viewport.
The element <a href="/United_States…k_City?map=sat">Satellite</a> falls outside the viewport.
The element <h4>Sea areas</h4> falls outside the viewport.
The element <a href="/Finland/Helsinki-Tallinn">Baltic Sea, FI</a> falls outside the viewport.
The element <a href="/Sweden/Sandhamn_-_Landsort">Baltic Sea, SE</a> falls outside the viewport.
The element <a href="/United_Kingdom/Thames">British Isles</a> falls outside the viewport.
The element <a href="/Spain/Alboran">Mediterranean West</a> falls outside the viewport.
The element <a href="/Turkey/Taurus">Mediterranean East</a> falls outside the viewport.
The element <h4>ForecaWeather App</h4> falls outside the viewport.
The element <img src="/img/footer-googleplay.png?2"> falls outside the viewport.
The element <img src="/img/footer-appstore-c.png?2"> falls outside the viewport.
The element <img src="/img/footer-windowsphone.png?2"> falls outside the viewport.
The element <img src="/img/foreca_logo_footer.png"> falls outside the viewport.

priority - 8 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <button id="pos_geode" type="submit" name="geode_submit"></button> is close to 1 other tap targets.

The tap target <a href="/United_States…/New_York_City" class="active green main">Local weather</a> is close to 1 other tap targets.

The tap target <a href="/United_States…_City?warnings" class="green main">Warnings</a> and 2 others are close to other tap targets.

The tap target <a href="/United_States…_City?map=symb">Symbol map</a> and 5 others are close to other tap targets.

The tap target <a href="/United_States…/Mountain_View">Mountain View, CA</a> and 4 others are close to other tap targets.

The tap target <a id="sail_mediteast" href="#">Mediterranean East</a> is close to 1 other tap targets.

The tap target <a href="/United_States…ork/browse.ski" class="ocean main">Ski Resorts</a> is close to 3 other tap targets.

The tap target <a href="/United_States…lpine_Mountain">Alpine Mountain,</a> and 16 others are close to other tap targets.

The tap target <a href="/browse"></a> is close to 1 other tap targets.

The tap target <a href="/United_States…tf=12h&lang=en" class="letter-link">°C</a> is close to 1 other tap targets.
The tap target <a href="/settings">Settings</a> is close to 1 other tap targets.
The tap target <a href="/United_States…ymb&zoom=state">NY</a> and 1 others are close to other tap targets.
The tap target <div class="ns-96mqi-e-5 headline">Find Directions & Visit Today</div> is close to 1 other tap targets.
The tap target <div class="ns-96mqi-e-7 store-name">adidas Outlet</div> is close to 1 other tap targets.
The tap target <div class="ns-96mqi-e-15 map-pin-icon"></div> is close to 1 other tap targets.
The tap target <div id="abgc" class="abgc"></div> is close to 2 other tap targets.
The tap target <div id="abgc" class="abgc"></div> is close to 1 other tap targets.
The tap target <div class="ns-7y017-e-5 headline">Save 40% Storewide This Week</div> is close to 1 other tap targets.
The tap target <div class="ns-7y017-e-5 headline">Save 40% Storewide This Week</div> is close to 1 other tap targets.
The tap target <div class="ns-7y017-e-7 store-name">adidas Outlet</div> is close to 2 other tap targets.
The tap target <div class="ns-7y017-e-15 map-pin-icon"></div> is close to 1 other tap targets.
The tap target <div id="abgc" class="abgc"></div> is close to 2 other tap targets.
The tap target <div id="abgc" class="abgc"></div> is close to 1 other tap targets.
The tap target <a href="https://corpor…om/en/contact/">Contact us</a> and 19 others are close to other tap targets.

foreca.com similar domains

Similar domains:

www.foreca.com
www.foreca.net
www.foreca.org
www.foreca.info
www.foreca.biz
www.foreca.us
www.foreca.mobi
www.oreca.com
www.foreca.com
www.coreca.com
www.fcoreca.com
www.cforeca.com
www.doreca.com
www.fdoreca.com
www.dforeca.com
www.roreca.com
www.froreca.com
www.rforeca.com
www.toreca.com
www.ftoreca.com
www.tforeca.com
www.goreca.com
www.fgoreca.com
www.gforeca.com
www.voreca.com
www.fvoreca.com
www.vforeca.com
www.freca.com
www.fireca.com
www.foireca.com
www.fioreca.com
www.fkreca.com
www.fokreca.com
www.fkoreca.com
www.flreca.com
www.folreca.com
www.floreca.com
www.fpreca.com
www.fopreca.com
www.fporeca.com
www.foeca.com
www.foeeca.com
www.foreeca.com
www.foereca.com
www.fodeca.com
www.fordeca.com
www.fodreca.com
www.fofeca.com
www.forfeca.com
www.fofreca.com
www.foteca.com
www.forteca.com
www.fotreca.com
www.forca.com
www.forwca.com
www.forewca.com
www.forweca.com
www.forsca.com
www.foresca.com
www.forseca.com
www.fordca.com
www.foredca.com
www.forrca.com
www.forerca.com
www.forreca.com
www.forea.com
www.forexa.com
www.forecxa.com
www.forexca.com
www.foreda.com
www.forecda.com
www.forefa.com
www.forecfa.com
www.forefca.com
www.foreva.com
www.forecva.com
www.forevca.com
www.forec.com
www.forecq.com
www.forecaq.com
www.forecqa.com
www.forecw.com
www.forecaw.com
www.forecwa.com
www.forecs.com
www.forecas.com
www.forecsa.com
www.forecz.com
www.forecaz.com
www.forecza.com
www.foreca.con

foreca.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.

foreca.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.

FORECA.COM Weather Forecast New York City - Foreca.com

foreca.com website information.

Weekly Rank Report

Advertisement

foreca.com Rank History

foreca.com whois

foreca.com server information

Servers Location

foreca.com desktop page speed rank

foreca.com Desktop Speed Test Quick Summary

priority - 6 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 3 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 3 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 2 Reduce server response time

In our test, your server responded in 0.36 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5.4KiB (45% reduction).

foreca.com Desktop Resources

foreca.com Desktop Resource Breakdown

foreca.com mobile page speed rank

foreca.com Mobile Speed Test Quick Summary

priority - 24 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 10 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 8 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 3 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 25.1KiB (20% reduction).

priority - 2 Reduce server response time

In our test, your server responded in 0.36 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 541B (48% reduction).

foreca.com Mobile Resources

foreca.com Mobile Resource Breakdown

foreca.com mobile page usability

foreca.com Mobile Usability Test Quick Summary

priority - 39 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,200 CSS pixels wide, but the viewport is only 447 CSS pixels wide. The following elements fall outside the viewport:

priority - 8 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

foreca.com similar domains

foreca.com Ping

foreca.com TRACEROUTE