Tools & Wizards About Us
corelove.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

corelove.com

Page Load Speed

10.6 sec in total

First Response

112 ms

Resources Loaded

5.2 sec

Page Rendered

5.3 sec

corelove.com screenshot

About Website

Welcome to corelove.com homepage info - get ready to check Corelove best content right away, or after learning these important things about corelove.com

Learn how to use the Immortal AI Assistant to edit your memory and upgrade your life.

Visit corelove.com

Key Findings

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

Performance Metrics

corelove.com performance score

0

Network Requests Diagram

corelove.com

112 ms

immortal.ai

1178 ms

wp-emoji-release.min.js

101 ms

aek5nnt.css

421 ms

style.min.css

117 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Corelove.com, 91% (72 requests) were made to Immortal.ai and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Immortal.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 352.0 kB (54%)

Content Size

649.9 kB

After Optimization

297.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Corelove.com main page is 649.9 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. 75% 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. HTML takes 333.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 291.9 kB

  • Original 333.0 kB
  • After minification 324.0 kB
  • After compression 41.1 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 291.9 kB or 88% of the original size.

Image Optimization

-30%

Potential reduce by 58.2 kB

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

CSS Optimization

-2%

Potential reduce by 2.0 kB

  • Original 120.8 kB
  • After minification 120.4 kB
  • After compression 118.8 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. Corelove.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 67 (92%)

Requests Now

73

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

corelove.com

corelove.com

112 ms

immortal.ai

immortal.ai

1178 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

101 ms

aek5nnt.css

aek5nnt.css

421 ms

style.min.css

style.min.css

117 ms

style.min.css

style.min.css

152 ms

style.min.css

style.min.css

152 ms

theme.min.css

theme.min.css

148 ms

frontend-lite.min.css

frontend-lite.min.css

206 ms

post-5.css

post-5.css

222 ms

style.basic.css

style.basic.css

223 ms

style-simple-red.css

style-simple-red.css

220 ms

elementor-icons.min.css

elementor-icons.min.css

238 ms

frontend-lite.min.css

frontend-lite.min.css

236 ms

all.min.css

all.min.css

328 ms

v4-shims.min.css

v4-shims.min.css

324 ms

global.css

global.css

337 ms

post-94.css

post-94.css

412 ms

post-70.css

post-70.css

389 ms

style.min.css

style.min.css

326 ms

font-awesome.min.css

font-awesome.min.css

511 ms

ha-70.css

ha-70.css

473 ms

post-37.css

post-37.css

470 ms

post-2770.css

post-2770.css

522 ms

style.css

style.css

471 ms

css

css

248 ms

fontawesome.min.css

fontawesome.min.css

545 ms

brands.min.css

brands.min.css

552 ms

solid.min.css

solid.min.css

551 ms

jquery.min.js

jquery.min.js

600 ms

jquery-migrate.min.js

jquery-migrate.min.js

592 ms

language-cookie.js

language-cookie.js

595 ms

v4-shims.min.js

v4-shims.min.js

592 ms

css

css

312 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

563 ms

widget-icon-list.min.css

widget-icon-list.min.css

560 ms

post-5158.css

post-5158.css

578 ms

post-4630.css

post-4630.css

576 ms

post-13133.css

post-13133.css

577 ms

post-11529.css

post-11529.css

649 ms

css

css

479 ms

cc437e79e27c514a6d3770986e647ee0.js

cc437e79e27c514a6d3770986e647ee0.js

559 ms

post-2806.css

post-2806.css

578 ms

animations.min.css

animations.min.css

554 ms

hello-frontend.min.js

hello-frontend.min.js

538 ms

asl-prereq.js

asl-prereq.js

514 ms

asl-core.js

asl-core.js

506 ms

asl-results-vertical.js

asl-results-vertical.js

530 ms

asl-autocomplete.js

asl-autocomplete.js

427 ms

asl-load.js

asl-load.js

423 ms

asl-wrapper.js

asl-wrapper.js

425 ms

happy-addons.min.js

happy-addons.min.js

443 ms

happy-addons-pro.js

happy-addons-pro.js

423 ms

anime.min.js

anime.min.js

3000 ms

jquery-numerator.min.js

jquery-numerator.min.js

354 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

345 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

295 ms

p.css

p.css

317 ms

webpack.runtime.min.js

webpack.runtime.min.js

304 ms

frontend-modules.min.js

frontend-modules.min.js

2759 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

2763 ms

wp-polyfill.min.js

wp-polyfill.min.js

2757 ms

hooks.min.js

hooks.min.js

2773 ms

i18n.min.js

i18n.min.js

2710 ms

frontend.min.js

frontend.min.js

2710 ms

waypoints.min.js

waypoints.min.js

2681 ms

core.min.js

core.min.js

2680 ms

frontend.min.js

frontend.min.js

2688 ms

elements-handlers.min.js

elements-handlers.min.js

2651 ms

jquery.sticky.min.js

jquery.sticky.min.js

2637 ms

immortal-ai-logo3.png

immortal-ai-logo3.png

672 ms

placeholder.png

placeholder.png

670 ms

AI-VISION3.png

AI-VISION3.png

697 ms

istockphoto-1355464281-170667a.jpeg

istockphoto-1355464281-170667a.jpeg

694 ms

fa-brands-400.woff

fa-brands-400.woff

256 ms

fa-solid-900.woff

fa-solid-900.woff

254 ms

fa-regular-400.woff

fa-regular-400.woff

252 ms

happy-icons.woff

happy-icons.woff

255 ms

invisible.js

invisible.js

435 ms

SEO Factors

corelove.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corelove.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 Corelove.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

corelove.com

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