JMF.PT José Maria da Fonseca - Vinhos

jmf.pt Website Information

Daily Unique Visits: 2,261

Daily Page Views: 6,783

Income Per Day: $20

Estimated Value: $7,200

This website is located in Portugal and is using following IP address 91.198.47.123. See the complete list of popular websites hosted in Portugal.

jmf.pt is registered under .PT top-level domain. Please check other sites in .PT zone.

Website jmf.pt is using the following name servers:

  • mns02.domaincontrol.com
  • mns01.domaincontrol.com

and is probably hosted by Claranet Portugal S.A. See the full list of other websites hosted by Claranet Portugal S.A.

The highest website jmf.pt position in Alexa rank database was 250365 and the lowest rank position was 957002. Current position of jmf.pt in Alexa rank database is 475731.

Desktop speed score of jmf.pt (84/100) is better than the results of 78.07% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of jmf.pt (89/100) is better than the results of 31.01% of other sites and means that the page is mobile-friendly.

Mobile speed score of jmf.pt (62/100) is better than the results of 59.44% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

jmf.pt Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


jmf.pt whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


jmf.pt server information

Servers Location

jmf.pt desktop page speed rank

Last tested: 2017-11-26


Desktop Speed Medium
84/100

jmf.pt Desktop Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://jmf.pt/js/vendor/modernizr-2.6.2.min.js
http://jmf.pt/js/vendor/jquery-1.9.1.min.js

Optimize CSS Delivery of the following:

http://jmf.pt/css/fonts.css
http://jmf.pt/css/00_normalize.css
http://jmf.pt/css/11_pre.css
http://jmf.pt/css/99_helpers.css

priority - 4Minify 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 35.9KiB (48% reduction).

Minifying http://jmf.pt/css/fonts.css could save 31.9KiB (50% reduction) after compression.
Minifying http://jmf.pt/css/00_normalize.css could save 1.6KiB (60% reduction) after compression.
Minifying http://jmf.pt/css/11_pre.css could save 1.5KiB (27% reduction).
Minifying http://jmf.pt/css/99_helpers.css could save 830B (56% reduction) after compression.

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 58% of the final above-the-fold content could be rendered with the full HTML response.

priority - 1Reduce server response time

priority - 1Enable 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 6.9KiB (67% reduction).

Compressing http://jmf.pt/css/11_pre.css could save 4.2KiB (70% reduction).
Compressing http://jmf.pt/ could save 2.7KiB (63% reduction).

priority - 1Optimize images

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

Optimize the following images to reduce their size by 6.9KiB (39% reduction).

Compressing http://jmf.pt/img/logo_vrt.png could save 1.1KiB (25% reduction).
Compressing http://jmf.pt/img/vinho_moderacao_up.png could save 1.1KiB (25% reduction).
Compressing http://jmf.pt/img/logo_hrz_pre.png could save 1.1KiB (31% reduction).
Compressing http://jmf.pt/img/btn_entrance_up.png could save 968B (53% reduction).
Compressing http://jmf.pt/img/btn_lang_pt_hover.png could save 967B (69% reduction).
Compressing http://jmf.pt/img/btn_lang_en_up.png could save 932B (67% reduction).
Compressing http://jmf.pt/img/big_bullet_black.png could save 912B (75% reduction).

priority - 0Leverage 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.google-analytics.com/analytics.js (2 hours)

priority - 0Minify 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.1KiB (25% reduction).

Minifying http://jmf.pt/ could save 1.1KiB (25% reduction).

jmf.pt Desktop Resource Breakdown

Total Resources17
Number of Hosts2
Static Resources15
JavaScript Resources3
CSS Resources4

jmf.pt mobile page speed rank

Last tested: 2017-10-27


Mobile Speed Bad
62/100

jmf.pt Mobile Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://jmf.pt/js/vendor/modernizr-2.6.2.min.js

Optimize CSS Delivery of the following:

http://jmf.pt/css/fonts.css
http://jmf.pt/css/00_normalize.css
http://jmf.pt/css/11_pre.css
http://jmf.pt/css/99_helpers.css

priority - 14Enable 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 140.2KiB (55% reduction).

Compressing http://jmf.pt/js/vendor/jquery-1.9.1.min.js could save 58.4KiB (64% reduction).
Compressing http://jmf.pt/css/fonts.css could save 55.4KiB (47% reduction).
Compressing http://jmf.pt/js/vendor/modernizr-2.6.2.min.js could save 9KiB (59% reduction).
Compressing http://jmf.pt/css/00_normalize.css could save 7.9KiB (74% reduction).
Compressing http://jmf.pt/css/11_pre.css could save 4.2KiB (70% reduction).
Compressing http://jmf.pt/ could save 2.7KiB (63% reduction).
Compressing http://jmf.pt/css/99_helpers.css could save 2.7KiB (65% reduction).

priority - 8Minify 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 79.2KiB (56% reduction).

Minifying http://jmf.pt/css/fonts.css could save 66.8KiB (55% reduction).
Minifying http://jmf.pt/css/00_normalize.css could save 8.1KiB (75% reduction).
Minifying http://jmf.pt/css/99_helpers.css could save 2.8KiB (68% reduction).
Minifying http://jmf.pt/css/11_pre.css could save 1.5KiB (27% reduction).

priority - 1Optimize images

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

Optimize the following images to reduce their size by 6.9KiB (39% reduction).

Compressing http://jmf.pt/img/logo_vrt.png could save 1.1KiB (25% reduction).
Compressing http://jmf.pt/img/vinho_moderacao_up.png could save 1.1KiB (25% reduction).
Compressing http://jmf.pt/img/logo_hrz_pre.png could save 1.1KiB (31% reduction).
Compressing http://jmf.pt/img/btn_entrance_up.png could save 968B (53% reduction).
Compressing http://jmf.pt/img/btn_lang_pt_hover.png could save 967B (69% reduction).
Compressing http://jmf.pt/img/btn_lang_en_up.png could save 932B (67% reduction).
Compressing http://jmf.pt/img/big_bullet_black.png could save 912B (75% reduction).

priority - 1Reduce server response time

priority - 1Leverage 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.google-analytics.com/analytics.js (2 hours)

priority - 0Minify 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.1KiB (25% reduction).

Minifying http://jmf.pt/ could save 1.1KiB (25% reduction).

jmf.pt Mobile Resource Breakdown

Total Resources16
Number of Hosts2
Static Resources14
JavaScript Resources3
CSS Resources4

jmf.pt mobile page usability

Last tested: 2017-10-27


Mobile Usability Good
89/100

jmf.pt Mobile Usability Test Quick Summary


priority - 10Configure the viewport

Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.

jmf.pt HTML validation

Errors

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 8 Column: 9 - 70
"...> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> ..."

Quote “"” in attribute name. Probable cause: Matching quote missing somewhere earlier.

Line: 50 Column: - 14
"...> <div style"clear:both; ma..." Line: 50 Column: - 41
"... margin:0 auto;"></div> ..."

Attribute “style"clear:both;” not allowed on element “div” at this point.

Line: 50 Column: 4 - 42
"...</div> <div style"clear:both; margin:0 auto;"></div>..."

Attribute “margin:0” not allowed on element “div” at this point.

Line: 50 Column: 4 - 42
"...</div> <div style"clear:both; margin:0 auto;"></div>..."

Attribute “auto;"” not allowed on element “div” at this point.

Line: 50 Column: 4 - 42
"...</div> <div style"clear:both; margin:0 auto;"></div>..."

The “align” attribute on the “div” element is obsolete. Use CSS instead.

Line: 55 Column: 17 - 50
"... <div id="logo_hrz" align="center"></div>..."

Warnings

Attribute “style"clear:both;” is not serializable as XML 1.0.

Line: 50 Column: 4 - 42
"...</div> <div style"clear:both; margin:0 auto;"></div>..."

Attribute “margin:0” is not serializable as XML 1.0.

Line: 50 Column: 4 - 42
"...</div> <div style"clear:both; margin:0 auto;"></div>..."

Attribute “auto;"” is not serializable as XML 1.0.

Line: 50 Column: 4 - 42
"...</div> <div style"clear:both; margin:0 auto;"></div>..."

jmf.pt similar domains

Similar domains:
www.jmf.com
www.jmf.net
www.jmf.org
www.jmf.info
www.jmf.biz
www.jmf.us
www.jmf.mobi
www.mf.pt
www.jmf.pt
www.nmf.pt
www.jnmf.pt
www.njmf.pt
www.hmf.pt
www.jhmf.pt
www.hjmf.pt
www.umf.pt
www.jumf.pt
www.ujmf.pt
www.imf.pt
www.jimf.pt
www.ijmf.pt
www.kmf.pt
www.jkmf.pt
www.kjmf.pt
www.mmf.pt
www.jmmf.pt
www.mjmf.pt
www.jf.pt
www.jnf.pt
www.jmnf.pt
www.jjf.pt
www.jmjf.pt
www.jjmf.pt
www.jkf.pt
www.jmkf.pt
www.jm.pt
www.jmc.pt
www.jmfc.pt
www.jmcf.pt
www.jmd.pt
www.jmfd.pt
www.jmdf.pt
www.jmr.pt
www.jmfr.pt
www.jmrf.pt
www.jmt.pt
www.jmft.pt
www.jmtf.pt
www.jmg.pt
www.jmfg.pt
www.jmgf.pt
www.jmv.pt
www.jmfv.pt
www.jmvf.pt

jmf.pt Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


jmf.pt TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.