Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 0

    Best Practices

  • 92

    SEO

    Google-friendlier than
    74% of websites

blog.xodo.com

PDF Productivity Tips & Tutorials | Xodo Blog

Page Load Speed

2.7 sec in total

First Response

134 ms

Resources Loaded

2.5 sec

Page Rendered

54 ms

blog.xodo.com screenshot

About Website

Welcome to blog.xodo.com homepage info - get ready to check Blog Xodo best content for Sri Lanka right away, or after learning these important things about blog.xodo.com

Master PDF productivity with our expert how-to guides and tips. Simplify your document workflows, and learn the best techniques for processing PDFs.

Visit blog.xodo.com

Key Findings

We analyzed Blog.xodo.com page load time and found that the first response time was 134 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

blog.xodo.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value8,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.101

89/100

15%

TTI (Time to Interactive)

Value24.5 s

0/100

10%

Network Requests Diagram

blog.xodo.com

134 ms

blog

2009 ms

osano.js

154 ms

lightbox_inline.js

383 ms

fonts.css

963 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Blog.xodo.com, 87% (62 requests) were made to Cdn.xodo.com and 4% (3 requests) were made to Lightboxcdn.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Xodo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.2 kB (1%)

Content Size

876.5 kB

After Optimization

867.4 kB

In fact, the total size of Blog.xodo.com main page is 876.5 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. 50% of websites need less resources to load. Javascripts take 852.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 7.0 kB

  • Original 9.7 kB
  • After minification 9.4 kB
  • After compression 2.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 7.0 kB or 72% of the original size.

JavaScript Optimization

-0%

Potential reduce by 2.0 kB

  • Original 852.7 kB
  • After minification 852.7 kB
  • After compression 850.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 213 B

  • Original 14.1 kB
  • After minification 14.1 kB
  • After compression 13.9 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. Blog.xodo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 55 (85%)

Requests Now

65

After Optimization

10

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

Accessibility Review

blog.xodo.com accessibility score

91

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

blog.xodo.com SEO score

92

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

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 Blog.xodo.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 Blog.xodo.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

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