5.8 sec in total
383 ms
4.7 sec
779 ms
Welcome to tpex.com homepage info - get ready to check TPEX best content right away, or after learning these important things about tpex.com
Visit tpex.comWe analyzed Tpex.com page load time and found that the first response time was 383 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tpex.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value8.1 s
2/100
25%
Value9.9 s
9/100
10%
Value180 ms
92/100
30%
Value0.864
4/100
15%
Value10.9 s
21/100
10%
383 ms
1017 ms
89 ms
258 ms
252 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 74% of them (120 requests) were addressed to the original Tpex.com, 20% (32 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Tpex.com.
Page size can be reduced by 4.9 MB (61%)
8.1 MB
3.2 MB
In fact, the total size of Tpex.com main page is 8.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 121.8 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 17.2 kB, which is 12% 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 121.8 kB or 86% of the original size.
Potential reduce by 2.6 MB
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. Obviously, TPEX needs image optimization as it can save up to 2.6 MB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 679.9 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 679.9 kB or 67% of the original size.
Potential reduce by 1.5 MB
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. Tpex.com needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 88% of the original size.
Number of requests can be reduced by 98 (78%)
126
28
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TPEX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 47 to 1 for CSS and as a result speed up the page load time.
tpex.com
383 ms
www.tpex.com
1017 ms
simplelightbox.min.css
89 ms
powerfolio_css.css
258 ms
owl.carousel.css
252 ms
owl.theme.default.min.css
253 ms
pwrgrids_css.css
254 ms
all.css
45 ms
pgflio_portfolio_css.css
272 ms
frontend.css
448 ms
block-style-index.css
335 ms
styles.css
338 ms
frontend.css
418 ms
bootstrap.min.css
424 ms
font-awesome.min.css
450 ms
jquery.fancybox.css
501 ms
magnific-popup.css
421 ms
htportfolio-vendors.css
587 ms
htportfolio-widgets.css
504 ms
header-footer-elementor.css
516 ms
frontend-lite.min.css
622 ms
swiper.min.css
537 ms
post-14.css
584 ms
global.css
588 ms
post-9.css
601 ms
post-1705.css
629 ms
htbbootstrap.css
749 ms
animation.css
669 ms
htmega-keyframes.css
674 ms
css
35 ms
geovana.css
685 ms
billyohio.css
709 ms
themify-font.min.css
713 ms
bicon.min.css
757 ms
animate.min.css
834 ms
slick.min.css
768 ms
owl.carousel.min.css
798 ms
meanmenu.min.css
802 ms
jquery-nice-select.min.css
829 ms
css
52 ms
theme-default.min.css
836 ms
blog-post.min.css
774 ms
helper.min.css
646 ms
theme-style.min.css
735 ms
style.min.css
669 ms
blocks.min.css
666 ms
responsive.min.css
661 ms
animations.min.css
647 ms
htmega-widgets.css
824 ms
jquery.min.js
587 ms
jquery-migrate.min.js
589 ms
frontend.js
583 ms
js.cookie.min.js
624 ms
imagesloaded.min.js
722 ms
isotope.pkgd.min.js
719 ms
packery-mode.pkgd.min.js
708 ms
simple-lightbox.min.js
686 ms
custom-portfolio-lightbox.js
657 ms
custom-portfolio.js
654 ms
owl.carousel.min.js
654 ms
pwrgrids-custom-js.js
639 ms
isotope.pkgd.min.js
612 ms
custom-portfolio-elementor.js
740 ms
index.js
698 ms
index.js
697 ms
analytics.js
685 ms
jquery.fancybox.min.js
661 ms
waypoints.js
654 ms
jquery.counterup.js
757 ms
jquery.magnific-popup.min.js
751 ms
popper.min.js
736 ms
bootstrap.min.js
708 ms
htportfolio-jquery-widgets-active.js
706 ms
popper.min.js
675 ms
htbbootstrap.js
731 ms
slick.min.js
726 ms
owl.carousel.min.js
714 ms
jquery-elevatezoom.js
672 ms
jquery-nice-select.js
708 ms
countdown.js
705 ms
navigation.js
726 ms
skip-link-focus-fix.js
715 ms
jquery.meanmenu.min.js
676 ms
retina.min.js
663 ms
jquery.onepage.nav.js
653 ms
main.js
650 ms
admin.js
707 ms
jquery-numerator.min.js
507 ms
htmega-widgets-active.js
514 ms
frontend.js
513 ms
webpack.runtime.min.js
526 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
223 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
224 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
224 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
227 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
224 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
272 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
226 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
224 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
272 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
273 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
273 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
273 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
272 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
275 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
274 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
274 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
275 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
276 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
276 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
276 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
276 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
277 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
277 ms
fa-solid-900.woff
163 ms
fa-regular-400.woff
163 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecatU9ih9_bz.ttf
277 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecatNNih9_bz.ttf
339 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecatHdih9_bz.ttf
338 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecatatih9_bz.ttf
336 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecatht-h9_bz.ttf
395 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecattN-h9_bz.ttf
703 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecat6t-h9_bz.ttf
336 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecatNN-h9_bz.ttf
396 ms
LYjndHr-klIgTfc40komjQ5OObazYp-6H94dBF-RX6nNRJfi-Gf55IgAecattN6h9_bz.ttf
396 ms
fa-brands-400.woff
201 ms
frontend-modules.min.js
518 ms
waypoints.min.js
570 ms
core.min.js
573 ms
frontend.min.js
576 ms
underscore.min.js
580 ms
wp-util.min.js
596 ms
embed
526 ms
frontend.min.js
562 ms
TPEX-Logo-NEW.png
525 ms
edge-stadium-atrium.jpg
614 ms
AdobeStock_715587535-scaled.jpeg
616 ms
Afbeelding13.jpg
535 ms
Portfolio-2.png
732 ms
Portfolio-3.png
571 ms
Portfolio-4.png
475 ms
Portfolio-5.png
567 ms
Portfolio-6.png
603 ms
Portfolio-7.png
559 ms
EDGE-Stadium-Scaled.png
561 ms
AdobeStock_787620908-scaled.jpeg
509 ms
Robert-Rosier-1024x683.png
666 ms
IMG_1219-1024x683.jpg
584 ms
IMG_1197-1024x683.jpg
587 ms
IMG_1122-1024x683.jpg
538 ms
IMG_1156-1024x683.jpg
569 ms
AdobeStock_805387045-scaled.jpeg
576 ms
Robert-Rosier-150x150.png
585 ms
LinkedIn-Edge-invests-in-TPEX-international-150x150.png
592 ms
Firefly_419677e7-b85b-47b9-b05b-e4fd9d98b5bb-150x150.jpeg
589 ms
Olympic-scaled-1-150x150.png
626 ms
Building-scaled-1-150x150.png
605 ms
Digital-twin-scaled-1-150x150.png
625 ms
Schneider-smart-buildings-scaled-1-150x150.png
595 ms
js
38 ms
search.js
4 ms
geometry.js
7 ms
main.js
15 ms
tpex.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
tpex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
tpex.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
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
![]()
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tpex.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Tpex.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.
tpex.com
Open Graph description is not detected on the main page of TPEX. 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: