12.5 sec in total
1.1 sec
10.9 sec
519 ms
Welcome to introye.com homepage info - get ready to check Introye best content right away, or after learning these important things about introye.com
Introye specialises in the collection, management, maintenance and sale of business-to-business information. We have extensive experience in the collation and management of databases.
Visit introye.comWe analyzed Introye.com page load time and found that the first response time was 1.1 sec and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
introye.com performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value3.6 s
60/100
25%
Value3.0 s
94/100
10%
Value260 ms
83/100
30%
Value0.007
100/100
15%
Value3.9 s
89/100
10%
1088 ms
537 ms
808 ms
533 ms
534 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 95% of them (60 requests) were addressed to the original Introye.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Redi.co.za. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Introye.com.
Page size can be reduced by 741.5 kB (50%)
1.5 MB
737.1 kB
In fact, the total size of Introye.com main page is 1.5 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. 35% of websites need less resources to load. Javascripts take 805.2 kB which makes up the majority of the site volume.
Potential reduce by 30.2 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 9.1 kB, which is 24% 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 30.2 kB or 81% of the original size.
Potential reduce by 34.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. Introye images are well optimized though.
Potential reduce by 632.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 632.0 kB or 78% of the original size.
Potential reduce by 45.1 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. Introye.com needs all CSS files to be minified and compressed as it can save up to 45.1 kB or 82% of the original size.
Number of requests can be reduced by 31 (50%)
62
31
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Introye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
introye.com
1088 ms
grid.css
537 ms
style.css
808 ms
search-form.css
533 ms
camera.css
534 ms
owl.carousel.css
539 ms
jquery.simplyscroll-1.0.4.css
548 ms
jquery.js
1806 ms
jquery-migrate-1.2.1.js
1295 ms
jquery.mobile.customized.min.js
1297 ms
camera.js
1570 ms
owl.carousel.js
1564 ms
jquery-ui.js
3356 ms
jquery.simplyscroll-1.0.4.js
1855 ms
jquery.mousewheel-3.0.6.pack.js
1855 ms
jquery.fancybox.css
2088 ms
jquery.fancybox.pack.js
2366 ms
jquery.fancybox-buttons.css
2338 ms
jquery.fancybox-buttons.js
2347 ms
jquery.fancybox-media.js
2347 ms
jquery.fancybox-thumbs.css
2605 ms
jquery.fancybox-thumbs.js
2854 ms
script.js
2876 ms
analytics.js
23 ms
logo.png
266 ms
preloader.gif
270 ms
redi-site-footer.png
614 ms
Advtech%20B+W.JPG
549 ms
Auto%20and%20General%20B+W.JPG
553 ms
Barloworld%20power%20B+W.JPG
544 ms
Discovery%20B+W.JPG
543 ms
Google%20B+W.JPG
756 ms
Jet%20Education%20B+W.JPG
766 ms
Liberty%20B+W.JPG
1057 ms
Linvar%20B+W.JPG
1058 ms
man.JPG
1094 ms
Mccarth.JPG
1091 ms
Nedbank%20B+W.JPG
1279 ms
Sanlam%20B+W.JPG
1302 ms
Standard%20bank%20B+W.JPG
1566 ms
Toyota%20B+W.JPG
1586 ms
vodacom%20B%20+%20W.JPG
1619 ms
SES%20B+W.JPG
1889 ms
call_me2.jpg
1791 ms
collect
14 ms
braces_white.png
1762 ms
jquery.cookie.js
2025 ms
device.min.js
2044 ms
tmstickup.js
2097 ms
jquery.easing.1.3.js
2241 ms
jquery.ui.totop.js
2287 ms
jquery.mousewheel.min.js
2339 ms
jquery.simplr.smoothscroll.min.js
2539 ms
superfish.js
2547 ms
jquery.mobilemenu.js
2624 ms
jquery.unveil.js
2761 ms
index_img01.jpg
540 ms
index_img03.jpg
536 ms
index_img02.jpg
542 ms
index_img04.jpg
540 ms
camera-loader.gif
537 ms
slide01.jpg
1617 ms
slide04.jpg
1793 ms
introye.com 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
introye.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
Page has valid source maps
introye.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Introye.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Introye.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.
introye.com
Open Graph description is not detected on the main page of Introye. 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: