1.7 sec in total
30 ms
1.4 sec
232 ms
Click here to check amazing Pma content for United States. Otherwise, check out these important facts you probably never knew about pma.com
IFPA represents companies from every segment of the global fresh produce and floral supply chain. We advocate, connect and guide to enhance members’ prosperity.
Visit pma.comWe analyzed Pma.com page load time and found that the first response time was 30 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
pma.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value10.5 s
0/100
25%
Value17.0 s
0/100
10%
Value29,100 ms
0/100
30%
Value0.163
72/100
15%
Value40.8 s
0/100
10%
30 ms
257 ms
24 ms
28 ms
33 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 64% of them (55 requests) were addressed to the original Pma.com, 19% (16 requests) were made to Use.typekit.net and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (796 ms) belongs to the original domain Pma.com.
Page size can be reduced by 358.0 kB (18%)
2.0 MB
1.7 MB
In fact, the total size of Pma.com main page is 2.0 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 112.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. This page needs HTML code to be minified as it can gain 27.3 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 112.1 kB or 87% of the original size.
Potential reduce by 43.7 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. Pma images are well optimized though.
Potential reduce by 175.7 kB
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 175.7 kB or 63% of the original size.
Potential reduce by 26.5 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. Pma.com needs all CSS files to be minified and compressed as it can save up to 26.5 kB or 86% of the original size.
Number of requests can be reduced by 29 (42%)
69
40
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pma.com
30 ms
www.pma.com
257 ms
VisitorIdentification.js
24 ms
gridset.css
28 ms
heapbox
33 ms
jqbx
32 ms
VendorStyles
28 ms
PMAStyles
62 ms
modernizr-2.6.2.min.js
29 ms
hsc7mtz.js
139 ms
customCssFile.css
94 ms
global.js
23 ms
jquery.min.js
29 ms
jquery-migrate-1.2.1.min.js
11 ms
jquery.js
37 ms
jquery.dataTables.min.js
78 ms
dataTables.responsive.min.js
25 ms
Vendor
77 ms
Velir
76 ms
VelirInit
76 ms
18 ms
2aed
33 ms
aquant.js
411 ms
border_striped.png
409 ms
mixshutterstock158340995.jpg
345 ms
pma-logo.png
341 ms
homepage_veggies_large.jpg
345 ms
eatbrighterhp.png
342 ms
spritesheet.png
341 ms
bg_map.png
339 ms
globalconnections.jpg
342 ms
sciencetech.jpg
341 ms
industrytalent.jpg
342 ms
issuesleadership.jpg
343 ms
greengiantfresh1.png
472 ms
driscolls1.png
473 ms
dudafarmfreshfoods1.png
469 ms
oceanmistfarms5.png
471 ms
chiquitafreshexpress1.png
470 ms
naturipefarms2.png
471 ms
monsanto3.png
525 ms
wellpictberries4.png
552 ms
melissas1.png
552 ms
oppy4.png
552 ms
robinsonfresh2.png
559 ms
sunkistgrowers3.png
558 ms
sysco4.png
577 ms
calavo.png
640 ms
taylorfarms1.png
642 ms
californiaavocadocommission1.png
655 ms
zespri2.png
656 ms
mastronardiproduce3.png
656 ms
earthboundfarm.png
767 ms
sunlightinternationaltransparent.png
734 ms
giumarra2transparentwidth185.png
796 ms
internationalpaper.png
768 ms
marianinutcompany1.png
751 ms
missionproducelogo2016web_60h.png
787 ms
p.gif
120 ms
ZAijeXEmjaox1Q11XIcc_RLHdouahtKKKGGEBnMiTvXffwxSggMmeMI6MK6f5Mb.eot
118 ms
icZIVYXuSyG5JWdMZuKdYjsB56aOPIkXCOEJB26svo3ffw2SggMmeMI6MK6f5MS.eot
121 ms
iEFC-E38_RR05lHCu_1mZowESu852_lf5fzDeJfbjISff4kQgsMmeMI6MK6f5MS.eot
120 ms
CaoCmCoKVH1JLu_85L0hmrusv5DS7rtnO19vJ7wA-06ffHPsgsMmeMI6MK6f5Mb.eot
121 ms
XT0aPQMEnUw8fEe59pUFMGLDowIr5BeE0ipUtF-q7_3ffwRSggMmeMI6MK6f5Mt.eot
121 ms
F1z4BUFRctDa7FtQ8gh02UIXlUtYpRaGlWowulge5SwffwVSggMmeMI6MK6f5gI.eot
124 ms
3T2viGt1Bqw9DyA8wb4zcAg-CzhamDJn2AKTZnowtsqffFVSggMmeMI6MK6f5gM.eot
118 ms
lQjq2OTzZpLfx3i_KR7uzC4D2KrduH_JpdIZFQbPgmSffw1SggMmeMI6MK6f5Mw.eot
124 ms
Ay4V9tU613lXBBvXIitf0l21pkfdMRx1Xi_aVEygPC9ffF2SggMmeMI6MK6f5Mj.eot
126 ms
NfMSgld0vwqrVwqs5vry4ZGkZiG-u9tiwkbHPb764hGffwnSggMmeMI6MK6f5Mw.eot
124 ms
2NEpJbdH3a98a0Ng1mTzxvHESh-tMSyV9N2BALsYUASffHAsgsMmeMI6MK6f5Mt.eot
124 ms
Mg_O_Z7AHEMadjUYzZ1M7xQ9fOUZqIndqJnnxs4j5uGffHcsgsMmeMI6MK6f5gI.eot
124 ms
W9k1wVKAuqI3WOtsf-8n2x_ZqVmLt98j8Y3VS00165jffHpsgsMmeMI6MK6f5gM.eot
166 ms
ODOkex7P_NE91FvNRQD63QNAed6d9dMFONGQKycJ0mJffH-sgsMmeMI6MK6f5Mj.eot
166 ms
pixel;r=1253223229;a=p-UYvHnaY817p_D;ezt=1;orderid=;revenue=;labels=_fp.event.Homepage;fpan=1;fpa=P0-441838557-1456757649638;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456757649638;tzo=-180;ref=;url=http%3A%2F%2Fwww.pma.com%2F;ogl=type.website%2Ctitle.Home%2Cdescription.%2Curl.http%3A%2F%2Fwww%252Epma%252Ecom%2F%2Cimage.www%252Epma%252Ecom
112 ms
gtm.js
57 ms
login.aspx
117 ms
bx_loader.gif
281 ms
bg_map_dark.png
291 ms
analytics.js
26 ms
linkid.js
13 ms
collect
12 ms
collect
56 ms
collect
22 ms
nr-885.min.js
17 ms
collect
18 ms
2ef4283d26
53 ms
pma.com accessibility score
pma.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pma.com 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
Links are not crawlable
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pma.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Pma.com 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.
pma.com
Open Graph description is not detected on the main page of Pma. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: