Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 61

    SEO

    Google-friendlier than
    22% of websites

imedi.ge

მთავარი - IMEDI

Page Load Speed

7.8 sec in total

First Response

456 ms

Resources Loaded

6.6 sec

Page Rendered

672 ms

imedi.ge screenshot

About Website

Visit imedi.ge now to see the best up-to-date IMEDI content for Georgia and also check out these interesting facts you probably never knew about imedi.ge

Imedi News Portal

Visit imedi.ge

Key Findings

We analyzed Imedi.ge page load time and found that the first response time was 456 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

imedi.ge performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value38.4 s

0/100

25%

SI (Speed Index)

Value35.8 s

0/100

10%

TBT (Total Blocking Time)

Value21,190 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.149

76/100

15%

TTI (Time to Interactive)

Value67.5 s

0/100

10%

Network Requests Diagram

imedi.ge

456 ms

main.css

170 ms

all.css

331 ms

calendar_styles.css

331 ms

jquery-1.8.3.min.js

831 ms

Our browser made a total of 220 requests to load all elements on the main page. We found that 60% of them (132 requests) were addressed to the original Imedi.ge, 12% (26 requests) were made to Share.xdevel.com and 10% (22 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Imedi.ge.

Page Optimization Overview & Recommendations

Page size can be reduced by 917.4 kB (12%)

Content Size

7.5 MB

After Optimization

6.6 MB

In fact, the total size of Imedi.ge main page is 7.5 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. 80% 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. Images take 6.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 69.6 kB

  • Original 83.4 kB
  • After minification 71.6 kB
  • After compression 13.8 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 11.9 kB, which is 14% 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 69.6 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 189.8 kB

  • Original 6.5 MB
  • After minification 6.3 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. IMEDI images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 592.9 kB

  • Original 884.8 kB
  • After minification 879.5 kB
  • After compression 291.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 592.9 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 65.2 kB

  • Original 77.9 kB
  • After minification 66.6 kB
  • After compression 12.7 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. Imedi.ge needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (33%)

Requests Now

217

After Optimization

146

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

Accessibility Review

imedi.ge accessibility score

68

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

High

[lang] attributes do not have a valid value

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

imedi.ge 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

imedi.ge SEO score

61

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

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Document uses plugins

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

    KA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imedi.ge can be misinterpreted by Google and other search engines. Our service has detected that Georgian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Imedi.ge 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

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