Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

apitransformer.com

API Transformer to Convert Your API Definition Files - APIMatic

Page Load Speed

7.6 sec in total

First Response

196 ms

Resources Loaded

6.4 sec

Page Rendered

1 sec

apitransformer.com screenshot

About Website

Welcome to apitransformer.com homepage info - get ready to check API Transformer best content for Sri Lanka right away, or after learning these important things about apitransformer.com

Convert your API Definition files to any format of choice in a matter of seconds with API Transformer.

Visit apitransformer.com

Key Findings

We analyzed Apitransformer.com page load time and found that the first response time was 196 ms and then it took 7.4 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

apitransformer.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value25.9 s

0/100

10%

TBT (Total Blocking Time)

Value43,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.101

89/100

15%

TTI (Time to Interactive)

Value60.8 s

0/100

10%

Network Requests Diagram

196 ms

826ff03e7fbbd68db5fbcf39c2bee2a2.css

86 ms

27d2852c16cff09fc327d8ebcae9f2b3.css

237 ms

75bfb804b8e8f8588be718daa2e45221.css

167 ms

7bd692925a241456e85f38201b7d709b.css

207 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Apitransformer.com, 29% (25 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Apimatic.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 258.1 kB (30%)

Content Size

846.7 kB

After Optimization

588.6 kB

In fact, the total size of Apitransformer.com main page is 846.7 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. 85% 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 616.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 175.6 kB

  • Original 207.2 kB
  • After minification 195.9 kB
  • After compression 31.6 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 175.6 kB or 85% of the original size.

Image Optimization

-13%

Potential reduce by 81.7 kB

  • Original 616.3 kB
  • After minification 534.6 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, API Transformer needs image optimization as it can save up to 81.7 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

-3%

Potential reduce by 746 B

  • Original 23.1 kB
  • After minification 23.1 kB
  • After compression 22.4 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.

Requests Breakdown

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

Requests Now

55

After Optimization

19

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

Accessibility Review

apitransformer.com accessibility score

88

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

apitransformer.com best practices score

83

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

apitransformer.com SEO score

79

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

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

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 Apitransformer.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 Apitransformer.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 data is detected on the main page of API Transformer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: