Tools & Wizards About Us
imere.org screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

imere.org

The Institute for Mystical Experience Research and Education

Page Load Speed

3 sec in total

First Response

258 ms

Resources Loaded

1.9 sec

Page Rendered

872 ms

imere.org screenshot

About Website

Welcome to imere.org homepage info - get ready to check Imere best content right away, or after learning these important things about imere.org

Share Your Mystical Experience with Us and Learn More About Mystical Experiences. Explore the Institute for Mystical Experience Research and Education (IMERE) Website Today.

Visit imere.org

Key Findings

We analyzed Imere.org page load time and found that the first response time was 258 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

imere.org performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

84/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

imere.org

258 ms

style.min.css

62 ms

mediaelementplayer-legacy.min.css

115 ms

wp-mediaelement.min.css

156 ms

views-frontend.css

158 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 72% of them (43 requests) were addressed to the original Imere.org, 15% (9 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Static.ctctcdn.com. The less responsive or slowest element that took the longest time to load (743 ms) belongs to the original domain Imere.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 206.8 kB (18%)

Content Size

1.2 MB

After Optimization

952.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imere.org main page is 1.2 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. 60% of websites need less resources to load. Images take 618.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 117.1 kB

  • Original 156.5 kB
  • After minification 155.7 kB
  • After compression 39.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 117.1 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 214 B

  • Original 618.5 kB
  • After minification 618.3 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. Imere images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 88.1 kB

  • Original 379.3 kB
  • After minification 379.3 kB
  • After compression 291.2 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 88.1 kB or 23% of the original size.

CSS Optimization

-28%

Potential reduce by 1.4 kB

  • Original 4.8 kB
  • After minification 4.8 kB
  • After compression 3.4 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. Imere.org needs all CSS files to be minified and compressed as it can save up to 1.4 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (64%)

Requests Now

50

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imere.org

imere.org

258 ms

style.min.css

style.min.css

62 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

115 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

156 ms

views-frontend.css

views-frontend.css

158 ms

css

css

34 ms

style.css

style.css

161 ms

toolset-common-es-frontend.js

toolset-common-es-frontend.js

166 ms

jquery.min.js

jquery.min.js

167 ms

jquery-migrate.min.js

jquery-migrate.min.js

177 ms

signup-form-widget.min.js

signup-form-widget.min.js

61 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

208 ms

navigation.js

navigation.js

214 ms

global.js

global.js

214 ms

search.js

search.js

302 ms

wpfront-scroll-top.min.js

wpfront-scroll-top.min.js

305 ms

core.min.js

core.min.js

305 ms

datepicker.min.js

datepicker.min.js

310 ms

mouse.min.js

mouse.min.js

312 ms

slider.min.js

slider.min.js

312 ms

jquery.ui.touch-punch.js

jquery.ui.touch-punch.js

309 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

309 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

308 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

373 ms

underscore.min.js

underscore.min.js

372 ms

wp-util.min.js

wp-util.min.js

369 ms

backbone.min.js

backbone.min.js

368 ms

wp-playlist.min.js

wp-playlist.min.js

371 ms

views-frontend.js

views-frontend.js

370 ms

scc-c2.min.js

scc-c2.min.js

11 ms

matomo.js

matomo.js

258 ms

phast.php

phast.php

257 ms

phast.php

phast.php

414 ms

phast.php

phast.php

300 ms

phast.php

phast.php

368 ms

phast.php

phast.php

306 ms

phast.php

phast.php

368 ms

phast.php

phast.php

387 ms

phast.php

phast.php

444 ms

phast.php

phast.php

393 ms

phast.php

phast.php

395 ms

phast.php

phast.php

496 ms

phast.php

phast.php

596 ms

phast.php

phast.php

498 ms

underscore-min.js

underscore-min.js

118 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBiEJow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBiEJow.ttf

29 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBiEJow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBiEJow.ttf

45 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiEJow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiEJow.ttf

69 ms

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGU3ms5qofd.ttf

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGU3ms5qofd.ttf

69 ms

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGU7Gs5qofd.ttf

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGU7Gs5qofd.ttf

60 ms

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGUOWw5qofd.ttf

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGUOWw5qofd.ttf

74 ms

I_urMpWdvgLdNxVLVQh_hiGOqw.ttf

I_urMpWdvgLdNxVLVQh_hiGOqw.ttf

115 ms

I_urMpWdvgLdNxVLVWx-hiGOqw.ttf

I_urMpWdvgLdNxVLVWx-hiGOqw.ttf

113 ms

I_urMpWdvgLdNxVLVUB5hiGOqw.ttf

I_urMpWdvgLdNxVLVUB5hiGOqw.ttf

143 ms

api.js

api.js

87 ms

recaptcha__en.js

recaptcha__en.js

58 ms

matomo.php

matomo.php

743 ms

signup-form-widget.css

signup-form-widget.css

16 ms

528e22723df566c912c148ba7cc1d9e4.json

528e22723df566c912c148ba7cc1d9e4.json

52 ms

1.png

1.png

55 ms

Accessibility Review

imere.org accessibility score

94

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

Document doesn't have a <title> element

High

Links do not have a discernible name

Best Practices

imere.org best practices score

75

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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

imere.org SEO score

81

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

Document doesn't have a <title> element

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 Imere.org 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 Imere.org 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

imere.org

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