f64.ro website information.
f64.ro domain name is registered by .RO top-level domain registry. See the other sites registred in .RO domain zone.
No name server records were found.
and probably website f64.ro is hosted by WIKIMEDIA - Wikimedia Foundation Inc., US web hosting company. Check the complete list of other most popular websites hosted by WIKIMEDIA - Wikimedia Foundation Inc., US hosting company.
According to Alexa traffic rank the highest website f64.ro position was 196306 (in the world). The lowest Alexa rank position was 230831. Now website f64.ro ranked in Alexa database as number 208685 (in the world).
Website f64.ro Desktop speed measurement score (48/100) is better than the results of 21.82% of other sites shows that the page desktop performance can be improved.
f64.ro Mobile usability score (89/100) is better than the results of 31.01% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of f64.ro (24/100) is better than the results of 6.28% 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-16-2024 | 208,685 | -1,332 |
| Nov-15-2024 | 207,353 | -188 |
| Nov-14-2024 | 207,165 | -2,863 |
| Nov-13-2024 | 204,302 | 0 |
| Nov-12-2024 | 204,302 | 0 |
| Nov-11-2024 | 204,302 | 0 |
| Nov-10-2024 | 204,302 | -2,163 |
Advertisement
f64.ro 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.
f64.ro 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.
% The WHOIS service offered by ROTLD and the access to the records in the ROTLD WHOIS database
% are provided for information purposes and to be used within the scope of technical or administrative
% necessities of Internet operation or to remedy legal problems. The use for other purposes,
% in particular for advertising and domain hunting, is not permitted.
% Without prejudice to the above, it is explicitly forbidden to extract, copy and/or use or re-utilise
% in any form and by any means (electronically or not) the whole or a quantitatively or qualitatively
% substantial part of the contents of the WHOIS database without prior and explicit permission by ROTLD,
% nor in any attempt hereof, to apply automated, electronic processes to ROTLD (or its systems).
% ROTLD cannot, under any circumstances, be held liable in case the stored information would prove
% to be wrong, incomplete or not accurate in any sense.
% You agree that any reproduction and/or transmission of data for commercial purposes will always
% be considered as the extraction of a substantial part of the content of the WHOIS database.
% By submitting the query you agree to abide by this policy and accept that ROTLD can take measures
% to limit the use of its WHOIS services in order to protect the privacy of its registrants or the
% integrity of the database.
% The ROTLD WHOIS service on port 43 never discloses any information concerning the registrant.
% Registrant information can be obtained through use of the web-based whois service available from
% the ROTLD website www.rotld.ro
Domain Name: f64.ro
Registered On: 2005-02-10
Expires On: 2033-06-06
Registrar: ICI - Registrar
Referral URL: http://www.rotld.ro
DNSSEC: Inactive
Nameserver: ns-1923.awsdns-48.co.uk
Nameserver: ns-1404.awsdns-47.org
Nameserver: ns-112.awsdns-14.com
Nameserver: ns-992.awsdns-60.net
Domain Status: OK
f64.ro server information
Servers Location
| IP Address |
|---|
| Country |
|---|
f64.ro desktop page speed rank
Last tested: 2017-05-21
f64.ro Desktop Speed Test Quick Summary
priority - 91 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 883.7KiB (49% reduction).
Compressing http://img.f64.ro/template_new/i/sprite_index.png?r=3 could save 174.5KiB (38% reduction).
Compressing http://img.f64.ro/images/img_index/idx/770_sony%20days_4289-821.jpg could save 98.8KiB (67% reduction).
Compressing http://img.f64.ro/images/banners/idx/770_canon_cashback_4260-186.jpg could save 97.5KiB (67% reduction).
Compressing http://img.f64.ro/images/banners/idx/770_Canon-70D_4209-172.jpg could save 83.2KiB (65% reduction).
Compressing http://img.f64.ro/template_new/i/site-fotocarte-bf-2016a.jpg could save 67.2KiB (64% reduction).
Compressing http://img.f64.ro/images/banners/idx/770_tamron_ob…ive-tele_p_124-142.jpg could save 58.7KiB (50% reduction).
Compressing http://img.f64.ro/template_new/i/carduri-hp5.jpg could save 53.8KiB (60% reduction).
Compressing http://img.f64.ro/images/background/skin_site_camp…otografie_sus_-613.jpg could save 35.7KiB (50% reduction).
Compressing http://img.f64.ro/images/banners/idx/770_nikon-D7200_p_497-484.jpg could save 27.5KiB (44% reduction).
Compressing http://img.f64.ro/images/products/nt_130/pentax-k-r-body-18566.jpg could save 7.7KiB (67% reduction).
Compressing http://logo.cauti.ro/img/logo_1.png?merchant_id=30…F%2Fwww.f64.ro%2F&ref= could save 1,010B (29% reduction).
Compressing http://img.f64.ro/template_new/i/btn_close_cookie_bar.png could save 978B (79% reduction).
Compressing http://img.f64.ro/template_new/i/click_bndl_top.png could save 899B (73% reduction).
Compressing http://img.f64.ro/template_new/i/click_bndl_bottom.png could save 894B (77% reduction).
Compressing http://img.f64.ro/template_new/i/cookie_bar.png could save 840B (68% reduction).
priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 blocking script resources and 1 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:
http://img.f64.ro/template_new/js/script_new.js?r=40
http://img.f64.ro/data/menu.js
http://img.f64.ro/template_new/js/script_details.js?p=5
http://d2tgfbvjf3q6hn.cloudfront.net/js/da0753.js
Optimize CSS Delivery of the following:
priority - 6 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:
http://static.hotjar.com/c/hotjar-445622.js?sv=5 (60 seconds)
http://assets.pinterest.com/js/pinit.js (3.8 minutes)
http://assets.pinterest.com/js/pinit_main.js?0.33450601529330015 (4.8 minutes)
http://d2tgfbvjf3q6hn.cloudfront.net/js/da0753.js (5 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-ZF83 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/325183061011564?v=2.7.10 (20 minutes)
https://connect.facebook.net/signals/config/522754144566495?v=2.7.10 (20 minutes)
http://bat.bing.com/bat.js (30 minutes)
http://f64-bud.gravityrd-services.com/js/f64/gr_reco5.min.js (30 minutes)
http://stats.g.doubleclick.net/dc.js (2 hours)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 6 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 55.2KiB (90% reduction).
priority - 5 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 47.7KiB (23% reduction).
Minifying http://d2tgfbvjf3q6hn.cloudfront.net/js/da0753.js could save 15.2KiB (18% reduction) after compression.
Minifying http://img.f64.ro/template_new/js/script_new.js?r=40 could save 7KiB (23% reduction) after compression.
Minifying http://www.f64.ro/template_new/js/carousel/jquery.carouFredSel-5.5.5.js could save 3.3KiB (22% reduction) after compression.
Minifying http://img.f64.ro/template_new/js/script_details.js?p=5 could save 1.5KiB (26% reduction) after compression.
Minifying http://www.f64.ro/template_new/js/jquery.easing.1.3.js could save 1.1KiB (58% reduction) after compression.
Minifying https://connect.facebook.net/signals/config/325183061011564?v=2.7.10 could save 699B (12% reduction) after compression.
Minifying https://connect.facebook.net/signals/config/522754144566495?v=2.7.10 could save 631B (79% reduction) after compression.
Minifying http://img.f64.ro/template_new/js/countdown/assets…wn/jquery.countdown.js could save 532B (42% reduction) after compression.
priority - 0 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 3.7KiB (17% reduction).
priority - 0 Reduce server response time
In our test, your server responded in 0.22 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 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.8KiB (11% reduction).
f64.ro Desktop Resources
| Total Resources | 101 |
| Number of Hosts | 34 |
| Static Resources | 68 |
| JavaScript Resources | 29 |
| CSS Resources | 3 |
f64.ro Desktop Resource Breakdown
f64.ro mobile page speed rank
Last tested: 2017-05-21
f64.ro Mobile Speed Test Quick Summary
priority - 241 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 2.3MiB (87% reduction).
Compressing http://img.f64.ro/images/img_index/idx/770_sony%20days_4289-821.jpg could save 98.8KiB (67% reduction).
Compressing http://img.f64.ro/images/banners/idx/770_canon_cashback_4260-186.jpg could save 97.5KiB (67% reduction).
Compressing http://img.f64.ro/images/banners/idx/770_card_alpha-bank_4262-537.jpg could save 91.8KiB (67% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/b_suna.png could save 32.7KiB (94% reduction).
Compressing http://img.f64.ro/images/banners/idx/770_nikon-D7200_p_497-484.jpg could save 27.5KiB (44% reduction).
Compressing http://img.f64.ro/images/products/b/Nikon-AF-S-NIKKOR-50mm-f-1-8G-18731.jpg could save 23.7KiB (65% reduction).
Compressing http://img.f64.ro/images/products/b/pentax-k-r-body-18566.jpg could save 23.6KiB (71% reduction).
Compressing http://img.f64.ro/images/products/b/Kingston-Mobil…rd-Reader-45670-99.jpg could save 18.7KiB (80% reduction).
Compressing http://img.f64.ro/images/products/b/microfibra-matin-m-6312-9517.jpg could save 17.6KiB (78% reduction).
Compressing http://img.f64.ro/images/products/b/fancier-wt-376…d-foto-video-13686.jpg could save 17.5KiB (77% reduction).
Compressing http://img.f64.ro/t_mobile/i/reducerea_zilei.jpg could save 13.2KiB (50% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/menu_org.jpg could save 4.6KiB (43% reduction).
Compressing http://img.f64.ro/t_mobile/i/reducerea_ore_minute.jpg could save 3.6KiB (55% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/inner-bg.jpg could save 3.5KiB (58% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/logo_mobile.png could save 2.9KiB (35% reduction).
Compressing http://m.f64.ro/t_mobile/i/alte_categorii.png could save 2.8KiB (63% reduction).
Compressing http://img.f64.ro/t_mobile/i/alte_categorii_bottom.png could save 2.7KiB (88% reduction).
Compressing http://m.f64.ro/t_mobile/i/alte_categorii_bg.png could save 2.7KiB (96% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/bg_resigilate.png could save 1.5KiB (28% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/bg_camere.png could save 1.1KiB (27% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/home_ico.png could save 1KiB (52% reduction).
Compressing http://img.f64.ro/t_mobile/i/timp_ramas.jpg could save 1KiB (32% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/mail_ico.png could save 1KiB (48% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/menu_bottom_arrow.png could save 946B (65% reduction).
Compressing http://img.f64.ro/t_mobile/i/mobile/cart_basket.png could save 901B (75% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/cauta1.png could save 871B (33% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/bottom_normal.png could save 852B (63% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/cauta2.png could save 838B (17% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/bg_telefoane.png could save 814B (27% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/right_top_bg.png could save 784B (56% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/bgLogin.png could save 778B (82% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/org2.png could save 774B (52% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/left_top_bg.png could save 754B (58% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/org1.png could save 751B (46% reduction).
Compressing http://m.f64.ro/t_mobile/i/mobile/top_bg_2.png could save 691B (68% reduction).
priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 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:
http://m.f64.ro/t_mobile/script.js
http://m.f64.ro/data/script.js
Optimize CSS Delivery of the following:
http://m.f64.ro/t_mobile/js/countdown/assets/countdown/jquery.countdown.css
priority - 9 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 86.9KiB (86% reduction).
Compressing http://f64-bud.gravityrd-services.com/grrec-f64-wa…4.ro%2F],[]&r=167f90e7 could save 28.1KiB (83% reduction).
Compressing https://us36.zopim.com/s/W/xdds/esSvVN2KeKSEW4D+/p/1495356007846 could save 3KiB (67% reduction).
Compressing https://us36.zopim.com/s/W/xdds/esSvVN2KeKSEW4D+/p/1495356007868 could save 666B (56% reduction).
priority - 6 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:
http://www.googletagmanager.com/gtm.js?id=GTM-ZF83 (15 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://connect.facebook.net/signals/config/522754144566495?v=2.7.10 (20 minutes)
http://bat.bing.com/bat.js (30 minutes)
http://f64-bud.gravityrd-services.com/js/f64/gr_reco5.min.js (30 minutes)
http://stats.g.doubleclick.net/dc.js (2 hours)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 2 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 23.5KiB (29% reduction).
Minifying http://m.f64.ro/data/script.js could save 3.9KiB (22% reduction) after compression.
Minifying http://connect.facebook.net/en_US/fbds.js could save 694B (33% reduction) after compression.
Minifying http://connect.facebook.net/signals/config/522754144566495?v=2.7.10 could save 631B (79% reduction) after compression.
Minifying http://m.f64.ro/t_mobile/js/countdown/assets/count…query.countdown.js?r=1 could save 532B (42% reduction) after compression.
priority - 1 Reduce server response time
In our test, your server responded in 0.25 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 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 1.8KiB (18% reduction).
f64.ro Mobile Resources
| Total Resources | 110 |
| Number of Hosts | 25 |
| Static Resources | 62 |
| JavaScript Resources | 40 |
| CSS Resources | 4 |
f64.ro Mobile Resource Breakdown
f64.ro mobile page usability
Last tested: 2017-05-21
f64.ro Mobile Usability Test Quick Summary
priority - 10 Configure the viewport
Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.
Configuring a viewport specifying width=device-width instead of width=640 will allow your page to adapt for devices of various widths. This may require additional work to adapt your styling for smaller screens.
priority - 1 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.
<a class="meshim_widget_…_TappingScreen"> is close to 1 other tap targets.<button type="button" class="slick-prev slick-arrow">Previous</button> and 1 others are close to other tap targets.<button type="button" class="slick-prev slick-arrow">Previous</button> and 1 others are close to other tap targets.<li id="slick-slide00" class="slick-active">1</li> and 4 others are close to other tap targets.<button type="button">1</button> is close to 10 other tap targets.<button type="button">1</button> and 4 others are close to other tap targets.<button type="button">2</button> and 3 others are close to other tap targets.<a href="http://m.f64.r…curi-huse.html" class="genti">Genti</a> is close to 1 other tap targets.f64.ro similar domains
www.f64.net
www.f64.org
www.f64.info
www.f64.biz
www.f64.us
www.f64.mobi
www.64.ro
www.f64.ro
www.c64.ro
www.fc64.ro
www.cf64.ro
www.d64.ro
www.fd64.ro
www.df64.ro
www.r64.ro
www.fr64.ro
www.rf64.ro
www.t64.ro
www.ft64.ro
www.tf64.ro
www.g64.ro
www.fg64.ro
www.gf64.ro
www.v64.ro
www.fv64.ro
www.vf64.ro
www.f4.ro
www.f6.ro
f64.ro 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.
f64.ro 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.