Tools & Wizards About Us

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

swiftdocs.in

SwiftDocs- CKYC - Document Management System(DMS) with Customer onboarding, KYC, eKYC,ekYC ,cKYCR,eKYC Integration,cKYC Integration,cKYCR inetegration...

Page Load Speed

10.5 sec in total

First Response

2.8 sec

Resources Loaded

7.3 sec

Page Rendered

440 ms

About Website

Visit swiftdocs.in now to see the best up-to-date Swift Docs content and also check out these interesting facts you probably never knew about swiftdocs.in

SwiftDocs- Document Management System(DMS) with Customer onboarding, KYC, eKYC,CkYC ,CKYCR, eKYC Integration,cKYC Integration,cKYCR inetegration,Central KYC Registry,CERSAI,eKYC software solution, cKY...

Visit swiftdocs.in

Key Findings

We analyzed Swiftdocs.in page load time and found that the first response time was 2.8 sec and then it took 7.7 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

swiftdocs.in performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value18.7 s

0/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.274

44/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

swiftdocs.in

2779 ms

css

41 ms

css

53 ms

bootstrap.min.css

1640 ms

animations.css

1096 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 86% of them (101 requests) were addressed to the original Swiftdocs.in, 11% (13 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Swiftdocs.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (59%)

Content Size

3.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Swiftdocs.in main page is 3.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. 75% 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 72.1 kB

  • Original 80.4 kB
  • After minification 51.7 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 28.7 kB, which is 36% 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 72.1 kB or 90% of the original size.

Image Optimization

-42%

Potential reduce by 633.8 kB

  • Original 1.5 MB
  • After minification 891.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. Obviously, Swift Docs needs image optimization as it can save up to 633.8 kB or 42% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 605.0 kB

  • Original 928.6 kB
  • After minification 884.4 kB
  • After compression 323.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 605.0 kB or 65% of the original size.

CSS Optimization

-88%

Potential reduce by 529.6 kB

  • Original 602.3 kB
  • After minification 485.9 kB
  • After compression 72.7 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. Swiftdocs.in needs all CSS files to be minified and compressed as it can save up to 529.6 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (52%)

Requests Now

100

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

swiftdocs.in accessibility score

76

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

swiftdocs.in best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

swiftdocs.in SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Swiftdocs.in 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 Swiftdocs.in main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Swift Docs. 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: