Tools & Wizards About Us
i-docs.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

i-docs.com

Homepage - i-DOCS

Page Load Speed

8.7 sec in total

First Response

446 ms

Resources Loaded

8.1 sec

Page Rendered

181 ms

i-docs.com screenshot

About Website

Welcome to i-docs.com homepage info - get ready to check I DOCS best content right away, or after learning these important things about i-docs.com

i-DOCS utilities solution is designed for companies who depend on our systems to ensure business continuity and to handle large quantities of sensitive

Visit i-docs.com

Key Findings

We analyzed I-docs.com page load time and found that the first response time was 446 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

i-docs.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value17,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

i-docs.com

446 ms

www.i-docs.com

1650 ms

k2.css

687 ms

bootstrap.css

1103 ms

template.css

845 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 97% of them (95 requests) were addressed to the original I-docs.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain I-docs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 794.2 kB (51%)

Content Size

1.6 MB

After Optimization

757.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I-docs.com main page is 1.6 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. 25% of websites need less resources to load. Images take 645.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 47.0 kB

  • Original 55.8 kB
  • After minification 52.8 kB
  • After compression 8.7 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 47.0 kB or 84% of the original size.

Image Optimization

-13%

Potential reduce by 86.2 kB

  • Original 645.0 kB
  • After minification 558.7 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. Obviously, I DOCS needs image optimization as it can save up to 86.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 375.1 kB

  • Original 515.7 kB
  • After minification 467.6 kB
  • After compression 140.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 375.1 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 285.8 kB

  • Original 334.9 kB
  • After minification 277.7 kB
  • After compression 49.0 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. I-docs.com needs all CSS files to be minified and compressed as it can save up to 285.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (31%)

Requests Now

96

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I DOCS. 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 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

i-docs.com

i-docs.com

446 ms

www.i-docs.com

www.i-docs.com

1650 ms

k2.css

k2.css

687 ms

bootstrap.css

bootstrap.css

1103 ms

template.css

template.css

845 ms

bootstrap-responsive.css

bootstrap-responsive.css

427 ms

template-responsive.css

template-responsive.css

572 ms

off-canvas.css

off-canvas.css

671 ms

megamenu.css

megamenu.css

709 ms

megamenu-responsive.css

megamenu-responsive.css

854 ms

megamenu.css

megamenu.css

927 ms

animate.css

animate.css

951 ms

mod_jaslideshowlite.css

mod_jaslideshowlite.css

982 ms

mod_jaslideshowlite-fade.css

mod_jaslideshowlite-fade.css

1120 ms

mootools-core.js

mootools-core.js

1848 ms

core.js

core.js

1197 ms

jquery.min.js

jquery.min.js

8 ms

k2.js

k2.js

1234 ms

caption.js

caption.js

1242 ms

mootools-more.js

mootools-more.js

2531 ms

bootstrap.js

bootstrap.js

1908 ms

off-canvas.js

off-canvas.js

1462 ms

script.js

script.js

1517 ms

menu.js

menu.js

1524 ms

responsive.js

responsive.js

1735 ms

crawler.js

crawler.js

1789 ms

script.js

script.js

1787 ms

system.css

system.css

1880 ms

custom.css

custom.css

1928 ms

jquery.validate.min.js

jquery.validate.min.js

2087 ms

leadGenForms.js

leadGenForms.js

1981 ms

system.css

system.css

144 ms

stylesheet.css

stylesheet.css

263 ms

logo.gif

logo.gif

271 ms

search-invert.png

search-invert.png

273 ms

sl-1_460_400.png

sl-1_460_400.png

420 ms

sl-2_460_400.png

sl-2_460_400.png

567 ms

sl-3_460_400.png

sl-3_460_400.png

1141 ms

sl-4_460_400.png

sl-4_460_400.png

715 ms

sl-5_460_400.png

sl-5_460_400.png

947 ms

sl-6_460_400.png

sl-6_460_400.png

831 ms

sl-nav-bg.png

sl-nav-bg.png

691 ms

sl-1_460_400_60_60.png

sl-1_460_400_60_60.png

833 ms

sl-2_460_400_60_60.png

sl-2_460_400_60_60.png

971 ms

sl-3_460_400_60_60.png

sl-3_460_400_60_60.png

996 ms

sl-4_460_400_60_60.png

sl-4_460_400_60_60.png

1097 ms

sl-5_460_400_60_60.png

sl-5_460_400_60_60.png

1111 ms

sl-6_460_400_60_60.png

sl-6_460_400_60_60.png

1229 ms

Position2_om.png

Position2_om.png

1230 ms

position3_cm.png

position3_cm.png

1275 ms

position1_pin.png

position1_pin.png

1357 ms

user0_einv.png

user0_einv.png

1392 ms

tell_a_friend.png

tell_a_friend.png

1406 ms

subscribe.png

subscribe.png

1500 ms

partners_b.png

partners_b.png

1634 ms

contactme.png

contactme.png

1559 ms

logo_wind-b.jpg

logo_wind-b.jpg

1686 ms

logo_vodafone-b.jpg

logo_vodafone-b.jpg

1651 ms

alpcot.png

alpcot.png

1677 ms

alpha_bank.png

alpha_bank.png

1778 ms

alstom.png

alstom.png

1820 ms

carrefour.png

carrefour.png

1962 ms

cyta.png

cyta.png

1966 ms

emporiki.png

emporiki.png

1962 ms

eurobank%20.png

eurobank%20.png

1954 ms

firstdata.png

firstdata.png

2052 ms

forthnet.png

forthnet.png

2096 ms

globul.png

globul.png

2220 ms

hol.png

hol.png

2210 ms

ga.js

ga.js

26 ms

__utm.gif

__utm.gif

11 ms

roboto-bold-webfont.woff

roboto-bold-webfont.woff

2230 ms

hsbc.png

hsbc.png

1971 ms

karcher.png

karcher.png

1907 ms

loterie.png

loterie.png

1811 ms

marfin.png

marfin.png

1814 ms

oracle.png

oracle.png

1797 ms

primotek.png

primotek.png

1694 ms

propan_2.png

propan_2.png

1756 ms

ptk.png

ptk.png

1701 ms

teb.png

teb.png

1794 ms

tellas.png

tellas.png

1784 ms

tik.png

tik.png

1683 ms

toshiba.png

toshiba.png

1676 ms

typografeio.png

typografeio.png

1724 ms

vodafone.png

vodafone.png

1685 ms

wind.png

wind.png

1807 ms

twitter.png

twitter.png

1773 ms

facebook.png

facebook.png

1691 ms

google.png

google.png

1650 ms

you_tube.png

you_tube.png

1737 ms

pinterest_white.png

pinterest_white.png

1684 ms

linkedin_white.png

linkedin_white.png

1746 ms

flag_fr.png

flag_fr.png

1672 ms

flag_de.png

flag_de.png

1667 ms

readmore-bg.png

readmore-bg.png

1652 ms

avt-mask.png

avt-mask.png

1728 ms

slideloading.gif

slideloading.gif

1687 ms

Accessibility Review

i-docs.com accessibility score

92

Accessibility Issues

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

High

Buttons do not have an accessible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

i-docs.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

i-docs.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-docs.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 I-docs.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.

Social Sharing Optimization

i-docs.com

Open Graph data is detected on the main page of I DOCS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: