3.2 sec in total
148 ms
2.3 sec
735 ms
Click here to check amazing Freightya content. Otherwise, check out these important facts you probably never knew about freightya.com
We offer a flexing shipping experience from China. How we work guarantees you peace of mind. Ship from China to Nigeria, Europe, and America
Visit freightya.comWe analyzed Freightya.com page load time and found that the first response time was 148 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
freightya.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value9.5 s
0/100
25%
Value7.3 s
29/100
10%
Value2,970 ms
3/100
30%
Value0
100/100
15%
Value15.5 s
7/100
10%
148 ms
417 ms
132 ms
205 ms
210 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 87% of them (97 requests) were addressed to the original Freightya.com, 8% (9 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (873 ms) belongs to the original domain Freightya.com.
Page size can be reduced by 294.3 kB (16%)
1.9 MB
1.6 MB
In fact, the total size of Freightya.com main page is 1.9 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 739.4 kB which makes up the majority of the site volume.
Potential reduce by 118.3 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 118.3 kB or 82% of the original size.
Potential reduce by 20.5 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. Freightya images are well optimized though.
Potential reduce by 80.0 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 80.0 kB or 12% of the original size.
Potential reduce by 75.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. Freightya.com needs all CSS files to be minified and compressed as it can save up to 75.5 kB or 24% of the original size.
Number of requests can be reduced by 80 (85%)
94
14
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freightya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
freightya.com
148 ms
freightya.com
417 ms
all.min.css
132 ms
slick.min.css
205 ms
slick-theme.min.css
210 ms
jquery.fancybox.min.css
216 ms
blocks.style.css
273 ms
extendify-utilities.css
215 ms
bbpress.min.css
210 ms
styles.css
269 ms
style.css
278 ms
tutor-icon.min.css
279 ms
tutor.min.css
475 ms
tutor-front.min.css
342 ms
style.css
399 ms
style.css
336 ms
all.css
412 ms
style.css
339 ms
style.css
410 ms
css
28 ms
bootstrap.min.css
488 ms
owl.carousel.css
421 ms
owl.theme.css
464 ms
hover.css
466 ms
lightbox.css
485 ms
elementor-icons.min.css
494 ms
frontend.min.css
534 ms
swiper.min.css
550 ms
post-1152.css
544 ms
global.css
545 ms
post-11.css
547 ms
css
29 ms
fontawesome.min.css
550 ms
solid.min.css
603 ms
jquery.min.js
665 ms
jquery-migrate.min.js
625 ms
functions.js
623 ms
jquery.history.js
624 ms
manual-sticky-sidebar.js
625 ms
css
14 ms
api.js
45 ms
m-elementor.js
729 ms
frontend.blocks.js
658 ms
index.js
589 ms
index.js
583 ms
printomat.js
579 ms
print_elements.js
574 ms
wp-polyfill-inert.min.js
574 ms
regenerator-runtime.min.js
525 ms
wp-polyfill.min.js
603 ms
hooks.min.js
514 ms
i18n.min.js
515 ms
tutor.min.js
666 ms
quicktags.min.js
474 ms
core.min.js
464 ms
mouse.min.js
405 ms
sortable.min.js
395 ms
jquery.ui.touch-punch.js
505 ms
SocialShare.min.js
505 ms
tutor-front.min.js
482 ms
datepicker.min.js
455 ms
bootstrap.min.js
453 ms
toc.js
453 ms
timer.js
454 ms
appear.js
451 ms
parallax.min.js
476 ms
parallax.js
478 ms
owl.carousel.js
474 ms
imagesloaded.min.js
473 ms
masonry.min.js
472 ms
isotope.js
513 ms
imagesloaded.js
447 ms
advsearch.js
452 ms
magnific-popup.min.js
453 ms
after-load-requestcall.js
454 ms
theme.js
455 ms
voting-front.js
353 ms
index.js
356 ms
webpack.runtime.min.js
363 ms
frontend-modules.min.js
369 ms
waypoints.min.js
369 ms
frontend.min.js
368 ms
freightya-logo-pre.png
415 ms
logo-home.png
417 ms
home-slide-4.png
732 ms
sourcing.jpg
650 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpmJxAct.ttf
20 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJmJxAct.ttf
55 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuSJmJxAct.ttf
70 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulpmJxAct.ttf
72 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpiJxAct.ttf
71 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ6JxAct.ttf
72 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymu8Z6JxAct.ttf
73 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymulp6JxAct.ttf
69 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuv56JxAct.ttf
71 ms
fa-solid-900.woff
637 ms
fa-solid-900.ttf
873 ms
fa-solid-900.woff
524 ms
fa-regular-400.ttf
590 ms
fa-regular-400.woff
604 ms
eicons.woff
679 ms
et-line.woff
614 ms
warehousing0-consolidation.jpg
563 ms
shipping.jpg
563 ms
freightya-sourcing-china-procurement-1.jpg
766 ms
freightya-sourcing-china-procurement-2.jpg
810 ms
danny-su_11zon-273x300.jpg
646 ms
team2-300x300.jpg
676 ms
ngozi-freightya-reviews_11zon-272x300.jpg
716 ms
footerfreightya_11zon.jpg
651 ms
recaptcha__en.js
67 ms
app.min.js
108 ms
freightya.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
freightya.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
freightya.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freightya.com 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 Freightya.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.
freightya.com
Open Graph data is detected on the main page of Freightya. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: