Tools & Wizards About Us
corpository.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

corpository.com

Corpository | Indian Company Information | Financials

Page Load Speed

3.7 sec in total

First Response

397 ms

Resources Loaded

3.2 sec

Page Rendered

54 ms

corpository.com screenshot

About Website

Click here to check amazing Corpository content for India. Otherwise, check out these important facts you probably never knew about corpository.com

Visit corpository.com

Key Findings

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

Performance Metrics

corpository.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value31.7 s

0/100

25%

SI (Speed Index)

Value19.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,130 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value28.9 s

0/100

10%

Network Requests Diagram

corpository.com

397 ms

corpository.com

1125 ms

plugin-ga-events-forwarder-browser-0.2.0-min.js.gz

19 ms

analytics-browser-2.2.1-min.js.gz

25 ms

js

60 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 62% of them (8 requests) were addressed to the original Corpository.com, 15% (2 requests) were made to Cdn.amplitude.com and 8% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Corpository.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (75%)

Content Size

3.1 MB

After Optimization

784.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Corpository.com 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. 15% of websites need less resources to load. Javascripts take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 63.4 kB

  • Original 89.7 kB
  • After minification 88.6 kB
  • After compression 26.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. 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 63.4 kB or 71% of the original size.

JavaScript Optimization

-72%

Potential reduce by 1.7 MB

  • Original 2.4 MB
  • After minification 2.4 MB
  • After compression 656.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 1.7 MB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 583.9 kB

  • Original 685.8 kB
  • After minification 683.2 kB
  • After compression 101.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. Corpository.com needs all CSS files to be minified and compressed as it can save up to 583.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

corpository.com

corpository.com

397 ms

corpository.com

corpository.com

1125 ms

plugin-ga-events-forwarder-browser-0.2.0-min.js.gz

plugin-ga-events-forwarder-browser-0.2.0-min.js.gz

19 ms

analytics-browser-2.2.1-min.js.gz

analytics-browser-2.2.1-min.js.gz

25 ms

js

js

60 ms

animate.min.css

animate.min.css

31 ms

scripts.6c1954a01181a430.js

scripts.6c1954a01181a430.js

1298 ms

moment.min.js

moment.min.js

18 ms

loading-logo-gif.gif

loading-logo-gif.gif

1490 ms

Roboto-Regular.d0bc87a819730d23.ttf

Roboto-Regular.d0bc87a819730d23.ttf

1293 ms

Roboto-Medium.9204c2aa0a88c808.ttf

Roboto-Medium.9204c2aa0a88c808.ttf

1303 ms

Roboto-Bold.c36a3fe042b96dc3.ttf

Roboto-Bold.c36a3fe042b96dc3.ttf

1313 ms

styles.7da80248e09a76a9.css

styles.7da80248e09a76a9.css

192 ms

Accessibility Review

corpository.com accessibility score

89

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

corpository.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

corpository.com SEO score

86

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

    N/A

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corpository.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Corpository.com main page’s claimed encoding is . 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

corpository.com

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