Your Website Score is

Similar Ranking

16
WORDPRESS › ERROR
starwards.org.uk
16
AUXILIADORA CAMPO GRANDE
auxiliadora-ms.g12.br
16
RASADNIK PROLEĆE KRUŠEVAC
rasadnikprolece.com
16
VIKSHASERVICES.COM – OFFICIAL WEBSITE
vikshaservices.com
16
TOMORROW WE VOTE | YOUTH ENGAGEMENT & VOTER REGISTRATION
tomorrowwevote.org
16
TS VERTEX
tsvertex.com

Latest Sites

9
YOUTUBE
youtube.com
19
SHOPCIAGA'S COLLECTIONS
ciagashop.gumroad.com
2
YOUTUBE
youtu.be
99
YOUTUBE
m.youtube.com

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
CloudFlare
CDN
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
WordPress
CMS

16 cocrea.world Last Updated: 2 days

Success 47% of passed verification steps
Warning 30% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 38%
Best Practices Desktop Score 100%
SEO Desktop Score 92%
Performance Mobile Score 16%
Best Practices Mobile Score 100%
SEO Mobile Score 92%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Title Tag 82 Characters
???? EXPLORE THE BEST SCRATCH GAMES. COCREA, PUBLISH A SCRATCH GAME WITH GANDI IDE
Meta Description 350 Characters
Pixel Survival V 0.3.4,Devil Corp - Modifiers Update,????????????????-???????????????????????????? ????????????????????????????????????????™,Sonic Celerity (Gandi IDE Version),[Gandi IDE] Zombie Apocalypse beta 1,Tile Tales,Timeless Worlds: Gathering and Warfare,Dizziness,Magnet Game Demo,Magna-Puzzle,Day and Night,Sunny and Luna,Magna - cat Pinbal
Effective URL 24 Characters
https://www.cocrea.world
Excerpt Page content
???? Explore the Best Scratch Games. Cocrea, publish a Scratch game with Gandi IDE
Google Preview Your look like this in google search result
???? EXPLORE THE BEST SCRATCH GAMES. COCREA, PUBLISH A SCRAT
https://www.cocrea.world
Pixel Survival V 0.3.4,Devil Corp - Modifiers Update,????????????????-???????????????????????????? ????????????????????????????????????????™,Sonic Cel
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~21.08 KB
Code Size: ~5.04 KB
Text Size: ~16.04 KB Ratio: 76.08%

Social Data

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Cumulative Layout Shift 0.36
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize third-party usage Third-party code blocked the main thread for 80 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
User Timing marks and measures 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Total Blocking Time 850 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve images in next-gen formats Est savings of 3,048 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce unused JavaScript Est savings of 847 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Largest Contentful Paint element 2,440 ms
This is the largest contentful element painted within the viewport
Avoid non-composited animations 3 animated elements found
Animations which are not composited can be janky and increase CLS
Avoid enormous network payloads Total size was 12,427 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids an excessive DOM size 781 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Reduce JavaScript execution time 1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Use efficient cache lifetimes Est savings of 10,934 KiB
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Server Backend Latencies 100 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Legacy JavaScript Est savings of 41 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Max Potential First Input Delay 360 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 3.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Preload Largest Contentful Paint image Est savings of 210 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP
Largest Contentful Paint 2.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Properly size images Est savings of 9,138 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Initial server response time was short Root document took 190 ms
Keep the server response time for the main document short because all other requests depend on it
Improve image delivery Est savings of 7,245 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Avoid serving legacy JavaScript to modern browsers Est savings of 14 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Defer offscreen images Est savings of 7 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Serve static assets with an efficient cache policy 46 resources found
A long cache lifetime can speed up repeat visits to your page
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Mobile

Mobile Screenshot
User Timing marks and measures 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Initial server response time was short Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 480 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid enormous network payloads Total size was 12,348 KiB
Large network payloads cost users real money and are highly correlated with long load times
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Speed Index 6.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Use efficient cache lifetimes Est savings of 10,929 KiB
A long cache lifetime can speed up repeat visits to your page
Reduce unused JavaScript Est savings of 801 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Minimize main-thread work 4.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy 46 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid non-composited animations 3 animated elements found
Animations which are not composited can be janky and increase CLS
Legacy JavaScript Est savings of 41 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Cumulative Layout Shift 0.638
Cumulative Layout Shift measures the movement of visible elements within the viewport
Server Backend Latencies 50 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Improve image delivery Est savings of 8,494 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Largest Contentful Paint element 9,990 ms
This is the largest contentful element painted within the viewport
Preload Largest Contentful Paint image Est savings of 1,210 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP
Avoids an excessive DOM size 740 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Largest Contentful Paint 10.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Defer offscreen images Est savings of 55 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Contentful Paint 3.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid large layout shifts 4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Reduce JavaScript execution time 2.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 1,210 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Properly size images Est savings of 9,062 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Minimize third-party usage Third-party code blocked the main thread for 180 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Avoid serving legacy JavaScript to modern browsers Est savings of 14 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Avoid long main-thread tasks 12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve images in next-gen formats Est savings of 3,048 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Time to Interactive 16.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
cocrea.co Already Registered
cocrea.us Available
cocrea.com Already Registered
cocrea.org Available
cocrea.net Already Registered
ccrea.world Available
docrea.world Available
rocrea.world Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Vary: Accept-Encoding
X-Powered-By: Next.js
Vary: Accept-Encoding
Server: TencentEdgeOne
Content-Encoding: gzip
Cache-Control: private, must-revalidate, no-cache, no-store, max-age=0
Transfer-Encoding: chunked
Connection: keep-alive
Date: Thu, 26 Jun 2025 16:49:27 GMT
EO-LOG-UUID: 11513930616952359840
EO-Cache-Status: MISS
DNS Records DNS Resource Records associated with a hostname
View DNS Records