Tools & Wizards About Us
crikey.io screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

crikey.io

Mobile Gaming Studio - Crikey

Page Load Speed

17.9 sec in total

First Response

1 sec

Resources Loaded

16.2 sec

Page Rendered

638 ms

crikey.io screenshot

About Website

Welcome to crikey.io homepage info - get ready to check Crikey best content right away, or after learning these important things about crikey.io

Crikey Games is a Sydney based mobile gaming development studio, that is focused on creating innovative quality mobile games, and promoting them on Android and iOS platforms to a global audience.

Visit crikey.io

Key Findings

We analyzed Crikey.io page load time and found that the first response time was 1 sec and then it took 16.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

crikey.io performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value23.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.624

10/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

crikey.io

1011 ms

9wvo7.css

244 ms

9wvo7.css

490 ms

9wvo7.css

697 ms

9wvo7.css

703 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 76% of them (68 requests) were addressed to the original Crikey.io, 17% (15 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (12.7 sec) belongs to the original domain Crikey.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.5 kB (7%)

Content Size

2.3 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Crikey.io main page is 2.3 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 147.1 kB

  • Original 177.3 kB
  • After minification 176.7 kB
  • After compression 30.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 147.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 6.8 kB

  • Original 1.7 MB
  • After minification 1.7 MB

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. Crikey images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.4 kB

  • Original 352.2 kB
  • After minification 352.2 kB
  • After compression 350.8 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

-1%

Potential reduce by 1.1 kB

  • Original 81.2 kB
  • After minification 81.2 kB
  • After compression 80.1 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. Crikey.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 51 (75%)

Requests Now

68

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

crikey.io

crikey.io

1011 ms

9wvo7.css

9wvo7.css

244 ms

9wvo7.css

9wvo7.css

490 ms

9wvo7.css

9wvo7.css

697 ms

9wvo7.css

9wvo7.css

703 ms

9wvo7.css

9wvo7.css

700 ms

9wvo7.css

9wvo7.css

706 ms

post-13.css

post-13.css

735 ms

9wvo7.css

9wvo7.css

733 ms

9wvo7.css

9wvo7.css

931 ms

9wvo7.css

9wvo7.css

931 ms

9wvo7.css

9wvo7.css

937 ms

post-14.css

post-14.css

941 ms

post-20.css

post-20.css

976 ms

post-3973.css

post-3973.css

979 ms

9wvo7.css

9wvo7.css

1161 ms

css

css

43 ms

9wvo7.css

9wvo7.css

1165 ms

9wvo7.css

9wvo7.css

1171 ms

9wvo7.css

9wvo7.css

1174 ms

jquery.min.js

jquery.min.js

1221 ms

jquery-migrate.min.js

jquery-migrate.min.js

1233 ms

akira-expanded

akira-expanded

140 ms

9wvo7.css

9wvo7.css

1395 ms

9wvo7.css

9wvo7.css

1396 ms

9wvo7.css

9wvo7.css

1403 ms

9wvo7.css

9wvo7.css

1407 ms

jquery.min.js

jquery.min.js

38 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

26 ms

post-1931.css

post-1931.css

1483 ms

post-3253.css

post-3253.css

1484 ms

post-359.css

post-359.css

2607 ms

9wvo7.css

9wvo7.css

1636 ms

css

css

37 ms

dlucc-init.js

dlucc-init.js

1646 ms

hello-frontend.min.js

hello-frontend.min.js

1645 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

1705 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

1711 ms

imagesloaded.min.js

imagesloaded.min.js

1867 ms

visibility.js

visibility.js

1881 ms

api.js

api.js

47 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1880 ms

webpack.runtime.min.js

webpack.runtime.min.js

1947 ms

frontend-modules.min.js

frontend-modules.min.js

1724 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1616 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1428 ms

wp-polyfill.min.js

wp-polyfill.min.js

1664 ms

hooks.min.js

hooks.min.js

1497 ms

i18n.min.js

i18n.min.js

1502 ms

frontend.min.js

frontend.min.js

1607 ms

waypoints.min.js

waypoints.min.js

1626 ms

core.min.js

core.min.js

1514 ms

frontend.min.js

frontend.min.js

1529 ms

elements-handlers.min.js

elements-handlers.min.js

1635 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

17 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

19 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

23 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

24 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

29 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

29 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

28 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

26 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

27 ms

background-image-1.jpg

background-image-1.jpg

1159 ms

slider-img.png

slider-img.png

1643 ms

Group-911.png

Group-911.png

1743 ms

Group-14498.png

Group-14498.png

2255 ms

Group-2921.png

Group-2921.png

2530 ms

Group-1234.png

Group-1234.png

1627 ms

Group-561.png

Group-561.png

1900 ms

Group-18910.png

Group-18910.png

2141 ms

elipse-6.png

elipse-6.png

2837 ms

Ellipse-3.png

Ellipse-3.png

2964 ms

Mask-group-bg-2.png

Mask-group-bg-2.png

2614 ms

Group-14504.png

Group-14504.png

3096 ms

image-403.png

image-403.png

12660 ms

Ellipse-369.png

Ellipse-369.png

3183 ms

NexaRegular.woff

NexaRegular.woff

2787 ms

AkiraExpanded-SuperBold-1.woff

AkiraExpanded-SuperBold-1.woff

2873 ms

NexaText-Book-1.woff

NexaText-Book-1.woff

2893 ms

fa-solid-900.woff

fa-solid-900.woff

3498 ms

fa-brands-400.woff

fa-brands-400.woff

3500 ms

recaptcha__en.js

recaptcha__en.js

66 ms

1.gif

1.gif

3517 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

11 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

10 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

13 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

13 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

13 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

13 ms

Accessibility Review

crikey.io accessibility score

98

Accessibility Issues

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

Links do not have a discernible name

Best Practices

crikey.io best practices score

67

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

crikey.io SEO score

100

Search Engine Optimization Advices

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

crikey.io

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