pfaf.org Website Information

Daily Unique Visits: 55,521

Daily Page Views: 333,126

Income Per Day: $666

Estimated Value: $479,520

This website is located in United States and is using following IP address 70.32.29.157. See the complete list of popular websites hosted in United States.

pfaf.org is registered under .ORG top-level domain. Please check other sites in .ORG zone.

Website pfaf.org is using the following name servers:

ns2.a2hosting.com
ns3.a2hosting.com
ns4.a2hosting.com
ns1.a2hosting.com

and is probably hosted by SERVERCENTRAL - Server Central Network, US. See the full list of other websites hosted by SERVERCENTRAL - Server Central Network, US.

The highest website pfaf.org position in Alexa rank database was 24209 and the lowest rank position was 26144. Current position of pfaf.org in Alexa rank database is 25832.

Desktop speed score of pfaf.org (61/100) is better than the results of 37.05% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of pfaf.org (59/100) is better than the results of 2.69% of other sites and means that the page is not mobile-friendly.

Mobile speed score of pfaf.org (45/100) is better than the results of 25.64% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

pfaf.org 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.

pfaf.org 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.

Domain Name: PFAF.ORG
Registry Domain ID: D27907610-LROR
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucows.com
Updated Date: 2021-04-26T22:59:09Z
Creation Date: 2000-05-26T22:56:43Z
Registry Expiry Date: 2022-05-26T22:56:43Z
Registrar Registration Expiration Date:
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: Plants For A Future
Registrant State/Province: Devon
Registrant Country: GB
Name Server: NS301.MY-HOSTING-PANEL.COM
Name Server: NS302.MY-HOSTING-PANEL.COM
Name Server: NS303.MY-HOSTING-PANEL.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2021-05-04T05:41:40Z

pfaf.org server information

Servers Location

pfaf.org desktop page speed rank

Last tested: 2017-06-01

Desktop Speed Bad

61/100

pfaf.org Desktop Speed Test Quick Summary

priority - 29Leverage 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://pfaf.org/jquery/jquery-1.12.3.min.js (expiration not specified)
http://pfaf.org/jquery/jquery-1.2.6.js (expiration not specified)
http://pfaf.org/jquery/jquery.alerts.css (expiration not specified)
http://pfaf.org/jquery/jquery.alerts.js (expiration not specified)
http://pfaf.org/user/css/horMenu.css (expiration not specified)
http://pfaf.org/user/css/stylesheet.css (expiration not specified)
http://pfaf.org/user/images/Banners/PFAF%20Slides3-01.png (expiration not specified)
http://pfaf.org/user/images/Banners/PFAF%20Slides3-02.png (expiration not specified)
http://pfaf.org/user/images/Banners/PFAF%20Slides3-03.png (expiration not specified)
http://pfaf.org/user/images/Banners/PFAF%20Slides3-04.png (expiration not specified)
http://pfaf.org/user/images/Banners/PFAF%20Slides3-05.png (expiration not specified)
http://pfaf.org/user/images/Banners/PFAF%20Slides3-06.png (expiration not specified)
http://pfaf.org/user/images/PFAF_homeV1b/submit_button.gif (expiration not specified)
http://pfaf.org/user/images/chris_small.jpg (expiration not specified)
http://pfaf.org/user/images/icons/1.png (expiration not specified)
http://pfaf.org/user/images/icons/10.png (expiration not specified)
http://pfaf.org/user/images/icons/11.png (expiration not specified)
http://pfaf.org/user/images/icons/12&13.png (expiration not specified)
http://pfaf.org/user/images/icons/14.png (expiration not specified)
http://pfaf.org/user/images/icons/15.png (expiration not specified)
http://pfaf.org/user/images/icons/16.png (expiration not specified)
http://pfaf.org/user/images/icons/17.png (expiration not specified)
http://pfaf.org/user/images/icons/18.png (expiration not specified)
http://pfaf.org/user/images/icons/19.png (expiration not specified)
http://pfaf.org/user/images/icons/2.png (expiration not specified)
http://pfaf.org/user/images/icons/20.png (expiration not specified)
http://pfaf.org/user/images/icons/21.png (expiration not specified)
http://pfaf.org/user/images/icons/22.png (expiration not specified)
http://pfaf.org/user/images/icons/23.png (expiration not specified)
http://pfaf.org/user/images/icons/24.png (expiration not specified)
http://pfaf.org/user/images/icons/3.png (expiration not specified)
http://pfaf.org/user/images/icons/4.png (expiration not specified)
http://pfaf.org/user/images/icons/5.png (expiration not specified)
http://pfaf.org/user/images/icons/6.png (expiration not specified)
http://pfaf.org/user/images/icons/7.png (expiration not specified)
http://pfaf.org/user/images/icons/8.png (expiration not specified)
http://pfaf.org/user/images/icons/9.png (expiration not specified)
http://pfaf.org/user/images/icons/arrows.png (expiration not specified)
http://pfaf.org/user/images/icons/facebook.png (expiration not specified)
http://pfaf.org/user/images/icons/home-3-24.ico (expiration not specified)
http://pfaf.org/user/images/icons/twiter.png (expiration not specified)
http://pfaf.org/user/images/pfaf_logo_bg.jpg (expiration not specified)
http://pfaf.org/user/images/searchbutton.jpg (expiration not specified)
http://pfaf.org/user/js/UserValidation.js (expiration not specified)
http://pfaf.org/user/js/jExpand.js (expiration not specified)
http://pfaf.org/user/nivo-slider/jquery.nivo.slider.js (expiration not specified)
http://pfaf.org/user/nivo-slider/nivo-slider.css (expiration not specified)
http://pfaf.org/user/nivo-slider/themes/bar/bar.css (expiration not specified)
http://pfaf.org/user/nivo-slider/themes/dark/dark.css (expiration not specified)
http://pfaf.org/user/nivo-slider/themes/default/arrows.png (expiration not specified)
http://pfaf.org/user/nivo-slider/themes/default/bullets.png (expiration not specified)
http://pfaf.org/user/nivo-slider/themes/default/default.css (expiration not specified)
http://pfaf.org/user/nivo-slider/themes/default/loading.gif (expiration not specified)
http://pfaf.org/user/nivo-slider/themes/light/light.css (expiration not specified)
https://apis.google.com/js/plusone.js (30 minutes)
http://cse.google.com/adsense/search/async-ads.js (60 minutes)
http://www.google.com/jsapi?autoload=%7B%22modules…22%3A%22en%22%7D%5D%7D (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 20Enable 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 190.6KiB (83% reduction).

Compressing http://pfaf.org/user/Default.aspx could save 167.8KiB (84% reduction).
Compressing http://pfaf.org/WebResource.axd?d=HNEoXLLTuX1g1rpy…1&t=635589255467565191 could save 16.4KiB (80% reduction).
Compressing http://pfaf.org/user/nivo-slider/themes/default/default.css could save 1.3KiB (65% reduction).
Compressing http://pfaf.org/user/nivo-slider/themes/light/light.css could save 1.3KiB (63% reduction).
Compressing http://pfaf.org/user/nivo-slider/themes/dark/dark.css could save 1.3KiB (63% reduction).
Compressing http://pfaf.org/user/nivo-slider/nivo-slider.css could save 1.2KiB (60% reduction).
Compressing http://pfaf.org/jquery/jquery.alerts.css could save 643B (57% reduction).
Compressing http://pfaf.org/user/css/horMenu.css could save 599B (59% reduction).

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

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

Remove render-blocking JavaScript:

http://pfaf.org/jquery/jquery-1.2.6.js
http://pfaf.org/jquery/jquery.alerts.js
http://pfaf.org/user/js/UserValidation.js
http://pfaf.org/WebResource.axd?d=HNEoXLLTuX1g1rpy…1&t=635589255467565191
http://pfaf.org/ScriptResource.axd?d=_cPKSHD2zoJfx…2&t=634163284800000000
http://pfaf.org/ScriptResource.axd?d=4JOKxdKjL_mjU…1&t=634163284800000000

Use asynchronous versions of the following scripts:

https://apis.google.com/js/plusone.js

Optimize CSS Delivery of the following:

http://www.jqueryscript.net/css/jquerysctipttop.css
http://pfaf.org/user/nivo-slider/themes/default/default.css
http://pfaf.org/user/nivo-slider/themes/light/light.css
http://pfaf.org/user/nivo-slider/themes/dark/dark.css
http://pfaf.org/user/nivo-slider/themes/bar/bar.css
http://pfaf.org/user/nivo-slider/nivo-slider.css
http://pfaf.org/jquery/jquery.alerts.css
http://pfaf.org/user/css/horMenu.css
http://pfaf.org/user/css/stylesheet.css

priority - 3Minify 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 31.3KiB (30% reduction).

Minifying http://pfaf.org/jquery/jquery-1.2.6.js could save 13.7KiB (46% reduction) after compression.
Minifying http://pfaf.org/ScriptResource.axd?d=_cPKSHD2zoJfx…2&t=634163284800000000 could save 6.9KiB (19% reduction) after compression.
Minifying http://pfaf.org/WebResource.axd?d=HNEoXLLTuX1g1rpy…1&t=635589255467565191 could save 5.9KiB (29% reduction).
Minifying http://pfaf.org/ScriptResource.axd?d=4JOKxdKjL_mjU…1&t=634163284800000000 could save 1.7KiB (18% reduction) after compression.
Minifying http://pfaf.org/user/nivo-slider/jquery.nivo.slider.js could save 1.6KiB (34% reduction) after compression.
Minifying http://pfaf.org/jquery/jquery.alerts.js could save 821B (39% reduction) after compression.
Minifying http://pfaf.org/user/js/UserValidation.js could save 752B (37% reduction) after compression.

priority - 2Minify 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 21.2KiB (11% reduction).

Minifying http://pfaf.org/user/Default.aspx could save 21.2KiB (11% reduction).

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.

71.3KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. However, if the HTML response were compressed, then the HTML required to render the above-the-fold content could be delivered in just 2 network round-trips. Enable compression for the HTML response in order to prioritize the visible content for this page.

Only about 46% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.

priority - 2Optimize images

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

Optimize the following images to reduce their size by 12.7KiB (53% reduction).

Compressing http://pfaf.org/user/images/pfaf_logo_bg.jpg could save 9.6KiB (59% reduction).
Compressing http://pfaf.org/user/images/chris_small.jpg could save 1.2KiB (61% reduction).
Compressing http://pfaf.org/user/images/searchbutton.jpg could save 836B (51% reduction).
Compressing http://pfaf.org/user/images/icons/facebook.png could save 614B (30% reduction).
Compressing http://pfaf.org/user/images/icons/twiter.png could save 573B (26% reduction).

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

Minifying http://www.google.com/uds/api/search/1.0/890e22867…9572ad4/default+en.css could save 3.9KiB (40% reduction) after compression.
Minifying http://pfaf.org/user/nivo-slider/nivo-slider.css could save 805B (40% reduction).
Minifying http://pfaf.org/user/css/stylesheet.css could save 580B (20% reduction) after compression.
Minifying http://pfaf.org/user/nivo-slider/themes/light/light.css could save 539B (26% reduction).
Minifying http://pfaf.org/user/nivo-slider/themes/dark/dark.css could save 537B (26% reduction).

priority - 0Reduce server response time

pfaf.org Desktop Resource Breakdown

Total Resources	77
Number of Hosts	9
Static Resources	68
JavaScript Resources	16
CSS Resources	11

pfaf.org mobile page speed rank

Last tested: 2017-05-18

Mobile Speed Bad

45/100

pfaf.org Mobile Speed Test Quick Summary

priority - 43Leverage 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 - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

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

Remove render-blocking JavaScript:

Use asynchronous versions of the following scripts:

https://apis.google.com/js/plusone.js

Optimize CSS Delivery of the following:

priority - 24Prioritize 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 31% of the final above-the-fold content could be rendered with the full HTML response.

priority - 20Enable 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 190.6KiB (83% reduction).

priority - 3Minify 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 31.3KiB (30% reduction).

priority - 2Minify 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 21.2KiB (11% reduction).

Minifying http://pfaf.org/user/Default.aspx could save 21.2KiB (11% reduction).

priority - 2Optimize images

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

Optimize the following images to reduce their size by 12.7KiB (53% reduction).

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

priority - 0Reduce server response time

pfaf.org Mobile Resource Breakdown

Total Resources	77
Number of Hosts	9
Static Resources	68
JavaScript Resources	16
CSS Resources	11

pfaf.org mobile page usability

Last tested: 2017-05-18

Mobile Usability Bad

59/100

pfaf.org Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

2017 Appeal ** renders only 6 pixels tall (15 CSS pixels).

Help PFAF to g…o complete it. renders only 6 pixels tall (15 CSS pixels).

Read more >> renders only 6 pixels tall (15 CSS pixels).

Suppliers and 4 others render only 6 pixels tall (15 CSS pixels).

Database Search Page: and 1 others render only 8 pixels tall (20 CSS pixels).

On our website…ble or other). and 11 others render only 6 pixels tall (15 CSS pixels).

Search techniques includes: renders only 6 pixels tall (15 CSS pixels).

When trying ne…r application. and 11 others render only 6 pixels tall (15 CSS pixels).

The main aim o…productivity. and 8 others render only 6 pixels tall (15 CSS pixels).

*** and 1 others render only 6 pixels tall (15 CSS pixels).

http://www.pfa…Aegle+marmelos and 7 others render only 6 pixels tall (15 CSS pixels).

2 and 79 others render only 6 pixels tall (15 CSS pixels).

Search for name: renders only 6 pixels tall (15 CSS pixels).

Flowering times and types and 24 others render only 6 pixels tall (15 CSS pixels).

Select any of…ile selecting. and 1 others render only 6 pixels tall (15 CSS pixels).

** renders only 5 pixels tall (14 CSS pixels).

2 and 5 others render only 6 pixels tall (15 CSS pixels).

Jan Feb…Dec and 1 others render only 6 pixels tall (15 CSS pixels).
Other Options: renders only 6 pixels tall (15 CSS pixels).
the full Speci…0 references). and 1 others render only 6 pixels tall (15 CSS pixels).
General Disclaimer renders only 7 pixels tall (18 CSS pixels).
No liability e…for a Future. and 4 others render only 6 pixels tall (15 CSS pixels).
PFAF Newsletter and 2 others render only 8 pixels tall (20 CSS pixels).
Why Perennial Plants? and 20 others render only 6 pixels tall (15 CSS pixels).
You…be at anytime. and 9 others render only 6 pixels tall (15 CSS pixels).
This work is l…lease view the and 4 others render only 4 pixels tall (10 CSS pixels).
Web Design & Management and 2 others render only 4 pixels tall (10 CSS pixels).

priority - 25Size 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 <a href="Default.aspx"></a> and 3 others are close to other tap targets.

The tap target <input type="button" class="gsc-search-button"> is close to 2 other tap targets.

The tap target <div class="gsc-clear-button"></div> is close to 1 other tap targets.

The tap target <a class="nivo-control active">1</a> is close to 1 other tap targets.

The tap target <a class="nivo-control">2</a> and 4 others are close to other tap targets.

The tap target <tr class="odd">Browse…mily, Habitate</tr> and 24 others are close to other tap targets.

The tap target <a href="/user/cmspage.aspx?pageid=76">Help with these terms</a> and 6 others are close to other tap targets.

The tap target <input id="ctl00_ContentP…kEdibleRating1" type="checkbox" name="ctl00$ContentP…kEdibleRating1"> and 81 others are close to other tap targets.

The tap target <label for="ctl00_ContentP…_chklstDecid_0">Deciduous</label> and 71 others are close to other tap targets.
The tap target

<input id="ctl00_ContentP…der1_btnSearch" type="submit" name="ctl00$ContentP…der1$btnSearch" class="roundcornerbutton grayButton">

and 1 others are close to other tap targets.
The tap target <a href="edibleuses.aspx">Edible Uses</a> and 20 others are close to other tap targets.
The tap target <input id="ctl00_btnSubmit" type="image" name="ctl00$btnSubmit"> is close to 1 other tap targets.
The tap target <a href="cmspage.aspx?pageid=136">Copyright</a> and 1 others are close to other tap targets.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

pfaf.org HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 121
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."

Attribute “http-equiv” not allowed on element “meta” at this point.

Line: 9 Column: 1 - 61
"...> <body> <meta http-equiv="refresh" content="0;URL=user/Default.aspx"> </bod..."

Element “meta” is missing one or more of the following attributes: “itemprop”, “property”.

Line: 9 Column: 1 - 61
"...> <body> <meta http-equiv="refresh" content="0;URL=user/Default.aspx"> </bod..."

pfaf.org similar domains

Similar domains:

www.pfaf.com
www.pfaf.net
www.pfaf.org
www.pfaf.info
www.pfaf.biz
www.pfaf.us
www.pfaf.mobi
www.faf.org
www.pfaf.org
www.ofaf.org
www.pofaf.org
www.opfaf.org
www.lfaf.org
www.plfaf.org
www.lpfaf.org
www.paf.org
www.pcaf.org
www.pfcaf.org
www.pcfaf.org
www.pdaf.org
www.pfdaf.org
www.pdfaf.org
www.praf.org
www.pfraf.org
www.prfaf.org
www.ptaf.org
www.pftaf.org
www.ptfaf.org
www.pgaf.org
www.pfgaf.org
www.pgfaf.org
www.pvaf.org
www.pfvaf.org
www.pvfaf.org
www.pff.org
www.pfqf.org
www.pfaqf.org
www.pfqaf.org
www.pfwf.org
www.pfawf.org
www.pfwaf.org
www.pfsf.org
www.pfasf.org
www.pfsaf.org
www.pfzf.org
www.pfazf.org
www.pfzaf.org
www.pfa.org
www.pfac.org
www.pfafc.org
www.pfacf.org
www.pfad.org
www.pfafd.org
www.pfadf.org
www.pfar.org
www.pfafr.org
www.pfarf.org
www.pfat.org
www.pfaft.org
www.pfatf.org
www.pfag.org
www.pfafg.org
www.pfagf.org
www.pfav.org
www.pfafv.org
www.pfavf.org

pfaf.org 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.

pfaf.org 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.

PFAF.ORG Website Information

pfaf.org Website Information

Advertisement

pfaf.org Alexa Rank

pfaf.org whois

pfaf.org server information

Servers Location

pfaf.org desktop page speed rank

pfaf.org Desktop Speed Test Quick Summary

priority - 29Leverage 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 - 20Enable 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 190.6KiB (83% reduction).

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

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

Remove render-blocking JavaScript:

Use asynchronous versions of the following scripts:

Optimize CSS Delivery of the following:

priority - 3Minify 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 31.3KiB (30% reduction).

priority - 2Minify 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 21.2KiB (11% reduction).

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.

priority - 2Optimize images

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

Optimize the following images to reduce their size by 12.7KiB (53% reduction).

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

priority - 0Reduce server response time

pfaf.org Desktop Resource Breakdown

pfaf.org mobile page speed rank

pfaf.org Mobile Speed Test Quick Summary

priority - 43Leverage 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 - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

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

Remove render-blocking JavaScript:

Use asynchronous versions of the following scripts:

Optimize CSS Delivery of the following:

priority - 24Prioritize 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.

priority - 20Enable 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 190.6KiB (83% reduction).

priority - 3Minify 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 31.3KiB (30% reduction).

priority - 2Minify 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 21.2KiB (11% reduction).

priority - 2Optimize images

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

Optimize the following images to reduce their size by 12.7KiB (53% reduction).

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

priority - 0Reduce server response time

pfaf.org Mobile Resource Breakdown

pfaf.org mobile page usability

pfaf.org Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 25Size 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.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

pfaf.org HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Attribute “http-equiv” not allowed on element “meta” at this point.

Element “meta” is missing one or more of the following attributes: “itemprop”, “property”.