Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

eprasa.com

eprasa.com

Page Load Speed

18.2 sec in total

First Response

954 ms

Resources Loaded

17 sec

Page Rendered

241 ms

eprasa.com screenshot

About Website

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

This domain may be for sale!

Visit eprasa.com

Key Findings

We analyzed Eprasa.com page load time and found that the first response time was 954 ms and then it took 17.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

eprasa.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.269

45/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

www3.eprasa.com

954 ms

style.css

428 ms

tlo.jpg

196 ms

o.gif

199 ms

main_t2.jpg

343 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Eprasa.com and no external sources were called. The less responsive or slowest element that took the longest time to load (954 ms) relates to the external source Www3.eprasa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.7 kB (26%)

Content Size

53.7 kB

After Optimization

39.9 kB

In fact, the total size of Eprasa.com main page is 53.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 36.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 10.5 kB

  • Original 13.5 kB
  • After minification 10.2 kB
  • After compression 3.0 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 24% 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 10.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 170 B

  • Original 36.7 kB
  • After minification 36.5 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. Eprasa images are well optimized though.

CSS Optimization

-89%

Potential reduce by 3.1 kB

  • Original 3.5 kB
  • After minification 2.7 kB
  • After compression 399 B

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. Eprasa.com needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (73%)

Requests Now

26

After Optimization

7

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

Accessibility Review

eprasa.com accessibility score

60

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

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

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 [lang] attribute

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

eprasa.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

eprasa.com SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eprasa.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Eprasa.com main page’s claimed encoding is iso-8859-2. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Eprasa. 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: