Tools & Wizards About Us
iminent.com screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

iminent.com

GET AMAZING EMOTICONS & ANIMATIONS

Page Load Speed

2.1 sec in total

First Response

55 ms

Resources Loaded

1.8 sec

Page Rendered

236 ms

iminent.com screenshot

About Website

Visit iminent.com now to see the best up-to-date Iminent content for Colombia and also check out these interesting facts you probably never knew about iminent.com

Visit iminent.com

Key Findings

We analyzed Iminent.com page load time and found that the first response time was 55 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

iminent.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

iminent.com

55 ms

en

13 ms

css

20 ms

responsive.css

10 ms

homepage.css

9 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 89% of them (31 requests) were addressed to the original Iminent.com, 9% (3 requests) were made to Iminentapi.pantherssl.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Iminent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 395.6 kB (13%)

Content Size

3.0 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iminent.com main page is 3.0 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. 35% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 22.1 kB

  • Original 30.6 kB
  • After minification 27.2 kB
  • After compression 8.4 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. This page needs HTML code to be minified as it can gain 3.3 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.1 kB or 72% of the original size.

Image Optimization

-10%

Potential reduce by 280.6 kB

  • Original 2.8 MB
  • After minification 2.5 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. Iminent images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 91.3 kB

  • Original 144.2 kB
  • After minification 136.7 kB
  • After compression 52.9 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 91.3 kB or 63% of the original size.

CSS Optimization

-28%

Potential reduce by 1.6 kB

  • Original 5.7 kB
  • After minification 5.7 kB
  • After compression 4.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. Iminent.com needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 28% of the original size.

Requests Breakdown

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

Requests Now

30

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iminent.com

iminent.com

55 ms

en

en

13 ms

css

css

20 ms

responsive.css

responsive.css

10 ms

homepage.css

homepage.css

9 ms

style.css

style.css

7 ms

DidacticPopup.css

DidacticPopup.css

9 ms

Offerscreen.css

Offerscreen.css

9 ms

modernizr-2.6.2.js

modernizr-2.6.2.js

444 ms

jquery-1.10.2.js

jquery-1.10.2.js

682 ms

getBrowser.js

getBrowser.js

421 ms

angular.js

angular.js

1198 ms

angular-route.js

angular-route.js

439 ms

cultureFactory.js

cultureFactory.js

439 ms

header.controller.js

header.controller.js

442 ms

footer.controller.js

footer.controller.js

442 ms

ApiFactory.js

ApiFactory.js

453 ms

content.controller.js

content.controller.js

453 ms

popupInstall.js

popupInstall.js

453 ms

Logo.png

Logo.png

54 ms

icon-menu.png

icon-menu.png

53 ms

iminent_background_1920.png

iminent_background_1920.png

554 ms

icon-iminent-white.png

icon-iminent-white.png

54 ms

icon-mouse.png

icon-mouse.png

55 ms

closeButton.png

closeButton.png

54 ms

350 ms

354 ms

353 ms

en.jpg

en.jpg

7 ms

de.jpg

de.jpg

8 ms

es.jpg

es.jpg

8 ms

fr.jpg

fr.jpg

8 ms

it.jpg

it.jpg

7 ms

pt.jpg

pt.jpg

8 ms

tr.jpg

tr.jpg

8 ms

Accessibility Review

iminent.com accessibility score

95

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.

Best Practices

iminent.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

iminent.com SEO score

78

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Iminent.com 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 Iminent.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

iminent.com

Open Graph description is not detected on the main page of Iminent. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: