4.4 sec in total
645 ms
3.2 sec
593 ms
Click here to check amazing PFE content. Otherwise, check out these important facts you probably never knew about pfe.express
We are an international freight forwarding company, offering intelligent global logistics solutions. We are more than a transport, warehousing, logistics and distribution business. Our business is all...
Visit pfe.expressWe analyzed Pfe.express page load time and found that the first response time was 645 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pfe.express performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value13.9 s
0/100
25%
Value12.4 s
3/100
10%
Value2,590 ms
4/100
30%
Value0.128
82/100
15%
Value23.8 s
1/100
10%
645 ms
35 ms
728 ms
52 ms
510 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 72% of them (100 requests) were addressed to the original Pfe.express, 18% (25 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pfe.express.
Page size can be reduced by 235.0 kB (8%)
2.8 MB
2.6 MB
In fact, the total size of Pfe.express main page is 2.8 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. Only a small number of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 103.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 103.5 kB or 80% of the original size.
Potential reduce by 97.2 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. PFE images are well optimized though.
Potential reduce by 34.2 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 77 (70%)
110
33
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PFE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.pfe.express
645 ms
sgr.css
35 ms
style.min.css
728 ms
bne-flyout.css
52 ms
styles.css
510 ms
cookie-law-info-public.css
63 ms
cookie-law-info-gdpr.css
60 ms
extendify-utilities.css
65 ms
spb-styles.css
104 ms
bootstrap.min.css
112 ms
font-awesome.min.css
88 ms
v4-shims.min.css
118 ms
iconfont.css
120 ms
main.css
143 ms
sf-responsive.css
161 ms
style.css
156 ms
uplift-custom.css
159 ms
sgr.js
178 ms
jquery.min.js
175 ms
jquery-migrate.min.js
176 ms
cookie-law-info-public.js
173 ms
imagesloaded.pkgd.min.js
208 ms
jquery.viewports.min.js
201 ms
plyr.js
211 ms
js
59 ms
js
109 ms
js
117 ms
email-decode.min.js
178 ms
css
37 ms
css
50 ms
cookie-law-info-table.css
206 ms
rs6.css
227 ms
index.js
228 ms
index.js
243 ms
recaptcha.js
233 ms
api.js
47 ms
rbtools.min.js
273 ms
rs6.min.js
268 ms
modernizr-custom.js
256 ms
spb-functions.min.js
296 ms
jquery.smartresize.min.js
308 ms
api.js
64 ms
pfe.js
311 ms
js.cookie.js
272 ms
bootstrap.min.js
285 ms
core.min.js
267 ms
accordion.min.js
285 ms
lightslider.min.js
277 ms
imagesloaded.min.js
262 ms
jquery.equalHeights.js
276 ms
jquery.infinitescroll.min.js
260 ms
jquery.stickyplugin.js
261 ms
jquery.touchSwipe.min.js
282 ms
jquery.transit.min.js
279 ms
jquery.appear.js
242 ms
jquery.auto-grow-input.min.js
240 ms
jquery.waypoints.min.js
271 ms
ilightbox.min.js
272 ms
owl.carousel.min.js
263 ms
jquery.isotope.min.js
259 ms
jquery.dotdotdot.js
295 ms
jquery.easing.1.3.js
301 ms
jquery.fittext.js
314 ms
jquery.hoverIntent.min.js
284 ms
jquery.stellar.min.js
294 ms
jquery.stickem.js
303 ms
jquery.timeago.js
313 ms
jquery.viewport.js
287 ms
jquery.visible.min.js
309 ms
functions.js
323 ms
jquery.equalheights.min.js
303 ms
isotope.pkgd.min.js
321 ms
jquery.parallax.min.js
288 ms
wpcf7-recaptcha-controls.js
304 ms
jquery.sidr.min.js
283 ms
PFE-Express-New-Logo_Reverse.png
71 ms
PFE_LinkedIn-Logo.png
713 ms
PFE_Twitter-Logo.png
68 ms
dummy.png
67 ms
PFE_IWD_730-x-560-480x368.jpg
67 ms
haydn-pound-ZT3i-6XW8J8-unsplash-480x368.jpg
714 ms
PFE_Ecommerce-Image-730-x-560-480x368.png
69 ms
PFE_Trust-Us_BW_1_c.jpg
70 ms
PFE_Home_Red-Icon_1.png
70 ms
PFE_Trust-Us_BW_2_03d410700d24aa0a2ee010553e6d5c79.jpg
125 ms
PFE_Home_Red-Icon_2.png
710 ms
PFE_Trust-Us_BW_3_40b80fb3e81934acb2877718e65e43e4.jpg
128 ms
PFE_Home_Red-Icon_3.png
129 ms
pfe-express-footer-logo-300x163.png
801 ms
AEO-logo-62.jpg
199 ms
bifa-logo_62x29.jpg
199 ms
ukwa-logo_64x14.jpg
262 ms
Approachable_UKAS_registered_c.jpg
262 ms
PFE_Home_Trust-Us_Parallax_896685e3b9e187279938a272fe3a7722-1.jpg
190 ms
www.pfe.express
587 ms
PFE_Home_Services_Ocean_v2_3d8e53071bef4901e13fc449d82d9a1c.jpg
585 ms
PFE_Home_Services_Air.jpg
1103 ms
PFE_Home_Services_Warehousing_811da20de8386c2be37b7109d0001dfa-1.jpg
1105 ms
PFE_Home_Services_Supply-Chain_9ea51363b9ae07086ab56b16dad6cc5b-1.jpg
673 ms
PFE_Home_Services_Customs_d0f8f6008eb52ad8dad78d549a5a0886-1.jpg
673 ms
PFE_Home_Services_EuropeanTravel_v2_0a9e256aaaaa4616b25eb3c69d186c11.jpg
1104 ms
PFE_Home_Services_Exports_52b278a0ed180a3b22891f57fdfcbfcf-1.jpg
682 ms
PFE_Home_Services_Intermodel_f348cefd0bc9abb70ccc1508632b0190.jpg
683 ms
PFE_Home_Footer_Parallax_8a680731df359bcb9c5f321a1e330604.jpg
684 ms
js
124 ms
analytics.js
169 ms
js
108 ms
S6uyw4BMUTPHjx4wWw.ttf
444 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
451 ms
S6u8w4BMUTPHh30AXC-v.ttf
451 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
447 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
451 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
450 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
449 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
450 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
454 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
455 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
530 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
454 ms
fa-solid-900.woff
1124 ms
fa-regular-400.woff
928 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
453 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf
454 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf
534 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf
534 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf
535 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf
533 ms
S6u8w4BMUTPHjxsAXC-v.ttf
531 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
534 ms
S6u-w4BMUTPHjxsIPx-oPCc.ttf
535 ms
S6u_w4BMUTPHjxsI5wq_Gwfo.ttf
537 ms
S6u_w4BMUTPHjxsI3wi_Gwfo.ttf
538 ms
nucleo-interface.ttf
927 ms
collect
364 ms
collect
356 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
441 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
443 ms
recaptcha__en.js
200 ms
recaptcha__en_gb.js
43 ms
pfe.express accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pfe.express 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
Browser errors were logged to the console
Page has valid source maps
pfe.express 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
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pfe.express can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pfe.express 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.
pfe.express
Open Graph data is detected on the main page of PFE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: