PDFNet View document taking long time to load

WebViewer Version: “@pdftron/webviewer”: “^10.0.0”,

Do you have an issue with a specific file(s)? Yes
Can you reproduce using one of our samples or online demos? Yes
Are you using the WebViewer server?
Does the issue only happen on certain browsers?
Is your issue related to a front-end framework? Yes
Is your issue related to annotations?

Please give a brief summary of your issue:

Hi Team, from 22nd Oct 2025, we are seeing latency issue in loading documents with webviewer . Before it loaded documents with in 4 seconds and now it is taking more than 15 seconds with same size of files.

Please help us out, if any changes need to be made.

Please describe your issue and provide steps to reproduce it:
(The more descriptive your answer, the faster we are able to help you)

Please provide a link to a minimal sample where the issue is reproducible:

Hello, I’m AiRon, an automated tech support bot :robot:
While you wait for one of our customer support representatives, I can help you with your question.


It seems like you’re experiencing performance issues with document loading times in WebViewer. This could be due to several factors such as changes in your environment, updates, or configuration issues.

Some things you can try:

  • Ensure that your server and network conditions are optimal and have not changed recently. Network latency can significantly affect load times.

  • Check the browser console for any errors or warnings that might indicate what is causing the slowdown.

  • Consider updating to a more recent version of WebViewer to benefit from performance improvements and bug fixes.

  • Review your implementation for any changes that might have introduced inefficiencies, especially if related to new features or integration with other systems.

  • Ensure that your WebViewer is properly configured and optimized for the types of documents you are loading. This might include settings related to rendering, caching, or resource loading.



Here are some resources that might help you:


Hopefully, this helps you solve your problem while you wait for a human to get back to you.

Hello @tejaswini.thota,

Thank you for posting on our forum.

If you have not already, see our FAQ here regarding some troubleshooting steps when encountering slow loading: https://docs.apryse.com/web/faq/slow-loading

To diagnose further we require the following information.

  1. What had changed since 22nd Oct 2025? Have you recently updated or changed your code?
  2. WebViewer constructor with all options defined
  3. Are you able to reproduce this issue with our latest release (Version 11.8)?
  4. Can you reproduce the issue using our samples (especially on our site)?
  5. Does the issue only occur in certain browsers and/or devices? If so what are the details?
  6. Sample PDFs used for testing

Best Regards,
Jacob Romano Carlsen
Web Development Support Engineer
Apryse Software Inc.

Hi,

Thank you for your reply.

  1. What had changed since 22nd Oct 2025? Have you recently updated or changed your code?
    No code changes related to document viewer.
  2. WebViewer constructor with all options defined
    import WebViewer, { WebViewerInstance } from ‘@pdftron/webviewer’;
    set reviewDocument(value: ReviewDocumentPickerOption) {
    if (!isUndefined(value?.documentUri)) {
    this._reviewDocument = value;
    this._showSpinner();
    /**
    * Fetches the Document Content
    */
    this._documentService
    .getReviewDocument(value.documentUri)
    .subscribe((arrayBuffer: ArrayBuffer) => {
    const uint8 = new Uint8Array(arrayBuffer);
    this._blob = new Blob([uint8]);
    this._loadDocument(this._blob);
    });
    }
    }
    ngAfterViewInit() {
    WebViewer(
    {
    path: ${this._appConfigState.environment.appBaseUrl}/assets/pdf-viewer,
    licenseKey: this._appConfigState.environment.apryseLicenseKey,
    css: ${this._appConfigState.environment.appBaseUrl}/assets/pdf-viewer-styles/styles.css,
    },
    this.viewer.nativeElement,
    ).then((instance) => {
    this.webViewerInstance = instance;
    this._setDocViewerTheme(‘light’);
    this._disableElements([
    ‘ribbons’,
    ‘ribbonsDropdown’,
    ‘selectToolButton’,
    ‘toggleNotesButton’,
    ‘toolsHeader’,
    ]);
    if (!isUndefined(this.reviewDocument?.documentUri)) {
    this._showSpinner();
    } else {
    this.webViewerInstance.UI.showWarningMessage({
    confirmBtnText: ‘’,
    title: “Couldn’t load the Document”,
    message:
    ‘The document either cannot be loaded from the URL or there are no available documents to display.’,
    // eslint-disable-next-line @typescript-eslint/no-empty-function
    onConfirm: () => {},
    // eslint-disable-next-line @typescript-eslint/no-empty-function
    onCancel: () => {},
    });
    }
    this._blob && this._loadDocument(this._blob);
    });
    }

/**

  • Loads the document
    /
    private _loadDocument(blob: Blob) {
    this.webViewerInstance?.UI.loadDocument(blob, {
    filename: this.reviewDocument.documentName.endsWith(‘.gz’)
    ? this.reviewDocument.documentName.slice(0, -3)
    : this.reviewDocument.documentName,
    });
    }
    /
    *
    • Service call
      */
      getReviewDocument(
      documentUri: string,
      contentType = ‘application/octet-stream’,
      responseType = ‘arraybuffer’,
      ): Observable {
return this.getOne<T>(
  `${this._environment.platformBackend}/file/download?uri=${encodeURI(documentUri)}`,
  {
    headers: new HttpHeaders({
      'Content-Type': contentType,
    }),
    responseType: responseType as 'json',
  },
);

}

  1. Are you able to reproduce this issue with our latest release (Version 11.8)?
    Not checked with latest version, because new version will have other behavior or UI changes.
  2. Can you reproduce the issue using our samples (especially on our site)?
    In https://showcase.apryse.com/ it is loading fine
  3. Does the issue only occur in certain browsers and/or devices? If so what are the details?
  4. Sample PDFs used for testing

original file (3).msg (2.3 MB)

1 Like

Hello @tejaswini.thota,

Thank you for the information.

If no code changes had occurred since the issue arose, it is likely that this is a network/environment related issue, and not related to WebViewer. We would recommend double checking to see if any network/environment configuration has been changed that could impact this.

Best Regards,
Jacob Romano Carlsen
Web Development Support Engineer
Apryse Software Inc.

1 Like