3.7 sec in total
780 ms
2.6 sec
277 ms
Click here to check amazing GlobalXS content. Otherwise, check out these important facts you probably never knew about globalxs.nl
GlobalXS - Uw glasvezelprovider die uw Alles-in-1: Internet Telefoon TV voor u regelt, van aanmelding tot aansluiting en alles wat u daarna nodig heeft.
Visit globalxs.nlWe analyzed Globalxs.nl page load time and found that the first response time was 780 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
globalxs.nl performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value7.9 s
3/100
25%
Value14.1 s
1/100
10%
Value3,060 ms
2/100
30%
Value0.021
100/100
15%
Value17.5 s
4/100
10%
780 ms
68 ms
217 ms
307 ms
319 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 77% of them (56 requests) were addressed to the original Globalxs.nl, 7% (5 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (955 ms) belongs to the original domain Globalxs.nl.
Page size can be reduced by 77.9 kB (8%)
987.4 kB
909.6 kB
In fact, the total size of Globalxs.nl main page is 987.4 kB. 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. Javascripts take 566.3 kB which makes up the majority of the site volume.
Potential reduce by 58.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 58.3 kB or 77% of the original size.
Potential reduce by 2 B
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. GlobalXS images are well optimized though.
Potential reduce by 4.6 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.
Potential reduce by 14.9 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. Globalxs.nl has all CSS files already compressed.
Number of requests can be reduced by 57 (88%)
65
8
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GlobalXS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.globalxs.nl
780 ms
js
68 ms
cf7ic-style.css
217 ms
style.min.css
307 ms
shortcodes.css
319 ms
styles.css
321 ms
front.min.css
322 ms
style.css
319 ms
custom.css
364 ms
wpcf7-redirect-frontend.min.css
408 ms
tablepress-combined.min.css
420 ms
js_composer_front_custom.css
648 ms
custom.css
420 ms
css
40 ms
bootstrap.min.css
527 ms
plugins.css
482 ms
font-icons.css
509 ms
style.css
633 ms
front.min.js
522 ms
jquery.min.js
724 ms
jquery-migrate.min.js
611 ms
js
64 ms
analytics.js
25 ms
css
18 ms
css
45 ms
rs6.css
522 ms
index.js
522 ms
index.js
607 ms
order-intake.js
664 ms
rbtools.min.js
758 ms
rs6.min.js
857 ms
wpcf7r-fe.js
664 ms
tracker.js
735 ms
api.js
44 ms
wp-polyfill-inert.min.js
774 ms
regenerator-runtime.min.js
773 ms
wp-polyfill.min.js
774 ms
index.js
836 ms
bootstrap.min.js
874 ms
fitvids.js
859 ms
easing.js
859 ms
isotope.pkgd.min.js
859 ms
goodshare.js
937 ms
appear.js
955 ms
collect
62 ms
collect
25 ms
countto.js
857 ms
easypiechart.js
763 ms
flexslider.js
756 ms
localscroll.js
786 ms
typed.js
833 ms
owlcarousel.js
852 ms
magnific.js
812 ms
flickity.js
772 ms
scrollreveal.js
765 ms
finalcountdown.js
804 ms
twitter.js
770 ms
scripts.js
763 ms
js_composer_front.min.js
785 ms
hotjar-1451242.js
144 ms
globalxs-header-logo.png
566 ms
dummy.png
566 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
70 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
71 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
109 ms
fontawesome-webfont.woff
685 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
111 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
112 ms
Global-foto.jpg
680 ms
GLOBAL-XS-slider.jpg
679 ms
icon54com.woff
583 ms
recaptcha__en.js
44 ms
modules.7b6d7646601d8cd7fb5f.js
44 ms
globalxs.nl 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
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.
globalxs.nl 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
globalxs.nl SEO score
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Globalxs.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Globalxs.nl 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.
globalxs.nl
Open Graph data is detected on the main page of GlobalXS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: