8.6 sec in total
219 ms
3.5 sec
4.9 sec
Click here to check amazing Globaleyez content. Otherwise, check out these important facts you probably never knew about globaleyez.net
Stop IP infringements against your brand. Whatever your industry and issues, globaleyez’s tailor-made solutions detect and eliminate distribution problems and IP threats to your brand both off- and on...
Visit globaleyez.netWe analyzed Globaleyez.net page load time and found that the first response time was 219 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
globaleyez.net performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value6.8 s
7/100
25%
Value6.4 s
40/100
10%
Value500 ms
58/100
30%
Value0.002
100/100
15%
Value9.1 s
33/100
10%
219 ms
325 ms
97 ms
113 ms
188 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 99% of them (88 requests) were addressed to the original Globaleyez.net, 1% (1 request) were made to Freeprivacypolicy.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Globaleyez.net.
Page size can be reduced by 888.5 kB (11%)
7.7 MB
6.9 MB
In fact, the total size of Globaleyez.net main page is 7.7 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. 65% of websites need less resources to load. Images take 7.5 MB which makes up the majority of the site volume.
Potential reduce by 111.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. 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 111.1 kB or 85% of the original size.
Potential reduce by 774.1 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. Globaleyez images are well optimized though.
Potential reduce by 981 B
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 2.2 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. Globaleyez.net has all CSS files already compressed.
Number of requests can be reduced by 22 (26%)
84
62
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Globaleyez. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
globaleyez.net
219 ms
325 ms
bootstrap.min.css
97 ms
slick.css
113 ms
slick-theme.css
188 ms
jquery.fancybox.min.css
210 ms
bootstrap_zcms.css
275 ms
font-awesome.min.css
273 ms
allgemein.css.php
291 ms
vtext.css
282 ms
show_bild.php
500 ms
en.png
359 ms
de.png
361 ms
index.php
740 ms
index.php
692 ms
index.php
534 ms
index.php
716 ms
index.php
651 ms
index.php
1276 ms
show_bild.php
1424 ms
cookie-consent.js
52 ms
jquery-3.5.1.min.js
743 ms
bootstrap.bundle.min.js
788 ms
jquery.fancybox.min.js
812 ms
jquery.scrollTo.min.js
826 ms
jquery.cycle2.min.js
835 ms
jquery.cycle2.carousel.min.js
882 ms
jquery.cycle2.shuffle.min.js
910 ms
jquery.cycle2.tile.min.js
914 ms
jquery.cycle2.scrollVert.min.js
925 ms
jquery.cycle2.swipe.min.js
977 ms
jquery.cycle2.flip.min.js
1020 ms
jquery.cycle2.caption2.min.js
1014 ms
jquery.cycle2.center.min.js
1015 ms
jquery.scrollme.min.js
1070 ms
jquery.matchHeight-min.js
1128 ms
slick.min.js
1132 ms
show_bild.php
1264 ms
show_bild.php
1265 ms
show_bild.php
1178 ms
show_bild.php
1236 ms
show_bild.php
1098 ms
show_bild.php
1091 ms
show_bild.php
1070 ms
show_bild.php
1075 ms
show_bild.php
1110 ms
show_bild.php
1054 ms
fontawesome-webfont.woff
1092 ms
index.php
1211 ms
index.php
980 ms
index.php
1085 ms
index.php
970 ms
index.php
869 ms
index.php
874 ms
index.php
863 ms
index.php
928 ms
index.php
893 ms
index.php
883 ms
index.php
896 ms
index.php
912 ms
show_bild.php
887 ms
show_bild.php
893 ms
show_bild.php
904 ms
show_bild.php
922 ms
show_bild.php
882 ms
show_bild.php
864 ms
show_bild.php
885 ms
show_bild.php
911 ms
show_bild.php
959 ms
show_bild.php
848 ms
slick.woff
699 ms
show_bild.php
746 ms
show_bild.php
761 ms
show_bild.php
784 ms
show_bild.php
905 ms
show_bild.php
836 ms
show_bild.php
963 ms
show_bild.php
814 ms
show_bild.php
831 ms
show_bild.php
855 ms
show_bild.php
865 ms
show_bild.php
863 ms
show_bild.php
889 ms
show_bild.php
888 ms
show_bild.php
886 ms
show_bild.php
834 ms
show_bild.php
833 ms
index.php
808 ms
ajax-loader.gif
803 ms
globaleyez.net 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
globaleyez.net 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
Page has valid source maps
globaleyez.net 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
Document doesn't have a valid hreflang
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Globaleyez.net 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 German language. Our system also found out that Globaleyez.net 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.
globaleyez.net
Open Graph description is not detected on the main page of Globaleyez. 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: