Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 66

    SEO

    Google-friendlier than
    35% of websites

presa.ge

მთავარი

Page Load Speed

10.4 sec in total

First Response

942 ms

Resources Loaded

8.4 sec

Page Rendered

1 sec

presa.ge screenshot

About Website

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

Visit presa.ge

Key Findings

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

Performance Metrics

presa.ge performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

942 ms

main.css

314 ms

jquery.min.js

48 ms

jquery-ui.min.js

79 ms

jquery.flash.min.js

354 ms

Our browser made a total of 227 requests to load all elements on the main page. We found that 51% of them (115 requests) were addressed to the original Presa.ge, 8% (19 requests) were made to Cdn3-c.imagestore.lv and 7% (15 requests) were made to Cdn3-a.imagestore.lv. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Presa.ge.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (39%)

Content Size

4.8 MB

After Optimization

2.9 MB

In fact, the total size of Presa.ge main page is 4.8 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. 85% 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 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 110.6 kB

  • Original 131.3 kB
  • After minification 128.7 kB
  • After compression 20.7 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 110.6 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 147.0 kB

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

JavaScript Optimization

-69%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 475.7 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 1.1 MB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 567.6 kB

  • Original 688.5 kB
  • After minification 676.1 kB
  • After compression 121.0 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. Presa.ge needs all CSS files to be minified and compressed as it can save up to 567.6 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

218

After Optimization

149

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

Accessibility Review

presa.ge accessibility score

57

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

presa.ge best practices score

75

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

SEO Factors

presa.ge SEO score

66

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

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

    KA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Presa.ge can be misinterpreted by Google and other search engines. Our service has detected that Georgian is used on the page, and it matches the claimed language. Our system also found out that Presa.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 description is not detected on the main page of Presa. 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: