Tools & Wizards About Us
papastasinos.gr screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

papastasinos.gr

papastasinos.gr

Page Load Speed

4.6 sec in total

First Response

413 ms

Resources Loaded

3.1 sec

Page Rendered

1.1 sec

papastasinos.gr screenshot

About Website

Click here to check amazing Papastasinos content. Otherwise, check out these important facts you probably never knew about papastasinos.gr

Visit papastasinos.gr

Key Findings

We analyzed Papastasinos.gr page load time and found that the first response time was 413 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

papastasinos.gr performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

papastasinos.gr

413 ms

papastasinos.gr

1211 ms

custom-frontend-lite.min.css

308 ms

post-825.css

398 ms

post-831.css

497 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 83% of them (50 requests) were addressed to the original Papastasinos.gr, 15% (9 requests) were made to Fonts.gstatic.com and 2% (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 Papastasinos.gr.

Page Optimization Overview & Recommendations

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

Content Size

2.8 MB

After Optimization

895.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Papastasinos.gr main page is 2.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. 60% of websites need less resources to load. CSS take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 211.2 kB

  • Original 240.1 kB
  • After minification 196.6 kB
  • After compression 29.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 43.5 kB, which is 18% 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 211.2 kB or 88% of the original size.

Image Optimization

-8%

Potential reduce by 48.6 kB

  • Original 585.1 kB
  • After minification 536.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. Papastasinos images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 360.2 kB

  • Original 522.0 kB
  • After minification 522.0 kB
  • After compression 161.8 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 360.2 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 1.3 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 167.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. Papastasinos.gr needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (74%)

Requests Now

47

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

papastasinos.gr

papastasinos.gr

413 ms

papastasinos.gr

papastasinos.gr

1211 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

308 ms

post-825.css

post-825.css

398 ms

post-831.css

post-831.css

497 ms

main.min.css

main.min.css

506 ms

main.css

main.css

708 ms

styles.css

styles.css

313 ms

contact-form-7-main.min.css

contact-form-7-main.min.css

405 ms

swiper.min.css

swiper.min.css

514 ms

post-701.css

post-701.css

492 ms

post-2163.css

post-2163.css

509 ms

ekiticons.css

ekiticons.css

788 ms

widget-styles.css

widget-styles.css

986 ms

responsive.css

responsive.css

602 ms

css

css

35 ms

jkiticon.css

jkiticon.css

612 ms

jquery.min.js

jquery.min.js

714 ms

jquery-migrate.min.js

jquery-migrate.min.js

704 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

713 ms

animations.min.css

animations.min.css

804 ms

sweetalert2.min.css

sweetalert2.min.css

812 ms

frontend.min.js

frontend.min.js

814 ms

hooks.min.js

hooks.min.js

883 ms

i18n.min.js

i18n.min.js

904 ms

index.js

index.js

905 ms

index.js

index.js

913 ms

frontend-script.js

frontend-script.js

915 ms

widget-scripts.js

widget-scripts.js

1137 ms

webpack.runtime.min.js

webpack.runtime.min.js

1135 ms

frontend-modules.min.js

frontend-modules.min.js

1135 ms

waypoints.min.js

waypoints.min.js

1135 ms

core.min.js

core.min.js

1135 ms

frontend.min.js

frontend.min.js

1135 ms

sticky-element.js

sticky-element.js

1136 ms

video-button.js

video-button.js

1136 ms

sweetalert2.min.js

sweetalert2.min.js

1136 ms

animate-circle.min.js

animate-circle.min.js

1136 ms

elementor.js

elementor.js

877 ms

banner-bg.jpg

banner-bg.jpg

267 ms

banner-bg-img.jpg

banner-bg-img.jpg

233 ms

IMG_0618-1-1-782x1024.jpg

IMG_0618-1-1-782x1024.jpg

236 ms

home-banner-img1.png

home-banner-img1.png

234 ms

diabetes-test_11748915.png

diabetes-test_11748915.png

233 ms

blood-pressure_9785892.png

blood-pressure_9785892.png

267 ms

biology_12838315.png

biology_12838315.png

327 ms

bg-imge.png

bg-imge.png

426 ms

Footer-bg-1.png

Footer-bg-1.png

328 ms

doctor_9821076.png

doctor_9821076.png

326 ms

elementskit.woff

elementskit.woff

231 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yO4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yO4a0Fg.ttf

58 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyO4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyO4a0Fg.ttf

81 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bCyO4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bCyO4a0Fg.ttf

123 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4ZmyO4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4ZmyO4a0Fg.ttf

122 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1O4a0Fg.ttf

123 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1O4a0Fg.ttf

123 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61O4a0Fg.ttf

123 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bC1O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bC1O4a0Fg.ttf

123 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC0O4a0Fg.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC0O4a0Fg.ttf

124 ms

jkiticon.woff

jkiticon.woff

321 ms

Accessibility Review

papastasinos.gr accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

papastasinos.gr best practices score

83

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

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

papastasinos.gr SEO score

85

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

    EL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Papastasinos.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it does not match the claimed English language. Our system also found out that Papastasinos.gr 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

papastasinos.gr

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