Tools & Wizards About Us
codecks.io screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

codecks.io

Playful Project Management for Game Development — Codecks

Page Load Speed

3.6 sec in total

First Response

330 ms

Resources Loaded

2.3 sec

Page Rendered

1 sec

codecks.io screenshot

About Website

Visit codecks.io now to see the best up-to-date Codecks content for United States and also check out these interesting facts you probably never knew about codecks.io

Playful Project Management Tool for Game Developers by Game Developers. Unique trading card game inspired design. Integrated Discord community management. Sign up for free!

Visit codecks.io

Key Findings

We analyzed Codecks.io page load time and found that the first response time was 330 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

codecks.io performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

codecks.io

330 ms

codecks.io

403 ms

www.codecks.io

379 ms

optimize.js

87 ms

js

71 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Codecks.io, 4% (1 request) were made to Googleoptimize.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Codecks.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.0 kB (27%)

Content Size

628.7 kB

After Optimization

459.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Codecks.io main page is 628.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. 25% of websites need less resources to load. Javascripts take 237.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 146.4 kB

  • Original 206.4 kB
  • After minification 206.2 kB
  • After compression 60.0 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 146.4 kB or 71% of the original size.

Image Optimization

-12%

Potential reduce by 21.8 kB

  • Original 184.9 kB
  • After minification 163.1 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, Codecks needs image optimization as it can save up to 21.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 823 B

  • Original 237.4 kB
  • After minification 237.3 kB
  • After compression 236.6 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 12 (63%)

Requests Now

19

After Optimization

7

  • Images
  • JavaScript

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

Network Requests Diagram

codecks.io

codecks.io

330 ms

codecks.io

codecks.io

403 ms

www.codecks.io

www.codecks.io

379 ms

optimize.js

optimize.js

87 ms

js

js

71 ms

polyfill-29634b956a00063adf5c.js

polyfill-29634b956a00063adf5c.js

585 ms

component---src-pages-index-js-82affef631c89005f4de.js

component---src-pages-index-js-82affef631c89005f4de.js

351 ms

component---src-pages-login-js-826316d9a5de84427f11.js

component---src-pages-login-js-826316d9a5de84427f11.js

352 ms

dda5e9f580e5aafde2b1112420362c9c50056a76-dc2909f8c56a20befb70.js

dda5e9f580e5aafde2b1112420362c9c50056a76-dc2909f8c56a20befb70.js

650 ms

commons-a280015ca03c0455d196.js

commons-a280015ca03c0455d196.js

267 ms

098f8663-660a8773a307898c51bd.js

098f8663-660a8773a307898c51bd.js

277 ms

b7106b16-8d8819ee35991e21c2e9.js

b7106b16-8d8819ee35991e21c2e9.js

523 ms

styles-e9d24b1846c7d6eb9685.js

styles-e9d24b1846c7d6eb9685.js

279 ms

app-3d498c486a2da491def4.js

app-3d498c486a2da491def4.js

806 ms

framework-cc313a9ee886d31327dc.js

framework-cc313a9ee886d31327dc.js

703 ms

webpack-runtime-239013b23f3d6ba7fcbf.js

webpack-runtime-239013b23f3d6ba7fcbf.js

621 ms

unity-574a935a84d57db50bd98103a59c41b2.png

unity-574a935a84d57db50bd98103a59c41b2.png

525 ms

wolfire-a8499d084be3abfec3893dac20a6e4c1.png

wolfire-a8499d084be3abfec3893dac20a6e4c1.png

526 ms

btf-1494ec11af3ccc40ed1dd92872ec0d43.png

btf-1494ec11af3ccc40ed1dd92872ec0d43.png

529 ms

paintbucket-3c3941fc20de402aaacece9378ea0a0d.png

paintbucket-3c3941fc20de402aaacece9378ea0a0d.png

531 ms

grimbart-tales-745018e9c8dc79f8d2c7c138e37ad1ec.png

grimbart-tales-745018e9c8dc79f8d2c7c138e37ad1ec.png

533 ms

chance-agency-994142d3ff72535493be3c62e1e77d84.png

chance-agency-994142d3ff72535493be3c62e1e77d84.png

535 ms

ebony-light-en-subset-b24d61f047cade31ea7c00bfcf05a6be.woff

ebony-light-en-subset-b24d61f047cade31ea7c00bfcf05a6be.woff

1097 ms

ebony-semibold-en-subset-75ba91c60e8b36417248bfa8fb165259.woff

ebony-semibold-en-subset-75ba91c60e8b36417248bfa8fb165259.woff

1098 ms

ebony-lightitalic-en-subset-3a0e58971ec1cf6d91f3dac34c40e0a8.woff

ebony-lightitalic-en-subset-3a0e58971ec1cf6d91f3dac34c40e0a8.woff

833 ms

ebony-semibolditalic-en-subset-37177cdb0a2c90723b7df62bc35fe071.woff

ebony-semibolditalic-en-subset-37177cdb0a2c90723b7df62bc35fe071.woff

833 ms

Accessibility Review

codecks.io 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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

codecks.io 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

codecks.io SEO score

90

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

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

High

Tap targets are not sized appropriately

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 Codecks.io 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 Codecks.io 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

codecks.io

Open Graph data is detected on the main page of Codecks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: