Tools & Wizards About Us
xls.repair screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

xls.repair

A powerful Microsoft Excel XLS file repair tool

Page Load Speed

6.7 sec in total

First Response

458 ms

Resources Loaded

3.4 sec

Page Rendered

2.8 sec

xls.repair screenshot

About Website

Welcome to xls.repair homepage info - get ready to check XLS best content right away, or after learning these important things about xls.repair

Microsoft XLS repair tool. How to repair corrupted XLS files with XLS Repair Kit? XLS Repair Kit is a powerful repair tool for corrupted *.xls and *.xlsx files.

Visit xls.repair

Key Findings

We analyzed Xls.repair page load time and found that the first response time was 458 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

xls.repair performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

458 ms

212 ms

745 ms

js

80 ms

cs.js

428 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Xls.repair, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Ut.recoverytoolbox.com. The less responsive or slowest element that took the longest time to load (898 ms) relates to the external source Online-file-repair.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 351.7 kB (64%)

Content Size

550.2 kB

After Optimization

198.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Xls.repair main page is 550.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 337.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 102.8 kB

  • Original 121.0 kB
  • After minification 109.1 kB
  • After compression 18.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. 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 102.8 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 91.8 kB
  • After minification 91.8 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. XLS images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 248.9 kB

  • Original 337.4 kB
  • After minification 337.2 kB
  • After compression 88.5 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 248.9 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (36%)

Requests Now

59

After Optimization

38

  • Images
  • JavaScript

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of XLS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

458 ms

212 ms

745 ms

js

js

80 ms

cs.js

cs.js

428 ms

logo.png

logo.png

306 ms

repairs.svg

repairs.svg

408 ms

about.svg

about.svg

414 ms

download.svg

download.svg

417 ms

online.svg

online.svg

439 ms

prices.svg

prices.svg

440 ms

review.svg

review.svg

447 ms

support.svg

support.svg

510 ms

contacts.svg

contacts.svg

516 ms

check-solid.svg

check-solid.svg

458 ms

online-white.svg

online-white.svg

481 ms

download-white.svg

download-white.svg

480 ms

star-fill.svg

star-fill.svg

605 ms

logo-excel-green-180.svg

logo-excel-green-180.svg

551 ms

access.png

access.png

554 ms

autocad.png

autocad.png

557 ms

corel-cdr.png

corel-cdr.png

581 ms

corel.png

corel.png

581 ms

outlook-express-dbx.png

outlook-express-dbx.png

651 ms

word-doc.png

word-doc.png

655 ms

word-docx.png

word-docx.png

659 ms

excel.png

excel.png

682 ms

foxpro.png

foxpro.png

683 ms

illustrator.png

illustrator.png

712 ms

lotusnotes.png

lotusnotes.png

705 ms

access-mdb.png

access-mdb.png

708 ms

sql-mdf.png

sql-mdf.png

712 ms

project-mpp.png

project-mpp.png

736 ms

lotusnotes_nsf.png

lotusnotes_nsf.png

737 ms

outlook-ost.png

outlook-ost.png

774 ms

outlook.png

outlook.png

807 ms

outlook-express.png

outlook-express.png

809 ms

pdf.png

pdf.png

813 ms

powerpoint.png

powerpoint.png

838 ms

powerpoint-ppt.png

powerpoint-ppt.png

839 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

898 ms

main.js

main.js

722 ms

dropzone.min.js

dropzone.min.js

824 ms

signalr.min.js

signalr.min.js

842 ms

common-min.js

common-min.js

640 ms

wizard-min.js

wizard-min.js

616 ms

loadreviews-min.js

loadreviews-min.js

686 ms

powerpoint-pptx.png

powerpoint-pptx.png

711 ms

project.png

project.png

649 ms

photoshop.png

photoshop.png

704 ms

outlook-pst.png

outlook-pst.png

712 ms

word-rtf.png

word-rtf.png

727 ms

sql.png

sql.png

728 ms

winrar.png

winrar.png

717 ms

word.png

word.png

716 ms

excel-xlsx.png

excel-xlsx.png

712 ms

osttopst.png

osttopst.png

696 ms

psttoeml.png

psttoeml.png

717 ms

outlookpassword.png

outlookpassword.png

698 ms

pdfpassword.png

pdfpassword.png

727 ms

star-empty.svg

star-empty.svg

719 ms

payproglobal.svg

payproglobal.svg

713 ms

email.png

email.png

696 ms

scrollup.svg

scrollup.svg

738 ms

prices-white.svg

prices-white.svg

709 ms

Accessibility Review

xls.repair accessibility score

97

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.

Best Practices

xls.repair best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

xls.repair SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

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 Xls.repair 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 Xls.repair 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

xls.repair

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