Tools & Wizards About Us
rimar.gr screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

rimar.gr

ΑΡΧΙΚΗ - RIMAR

Page Load Speed

13.4 sec in total

First Response

770 ms

Resources Loaded

12.5 sec

Page Rendered

123 ms

rimar.gr screenshot

About Website

Click here to check amazing RIMAR content for Greece. Otherwise, check out these important facts you probably never knew about rimar.gr

Κουτιά κουζίνας και ντουλάπας πορτάκια κουζίνας

Visit rimar.gr

Key Findings

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

Performance Metrics

rimar.gr performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.237

53/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

rimar.gr

770 ms

reset.css

298 ms

style.css

466 ms

index.css

468 ms

jquery.js

625 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 90% of them (38 requests) were addressed to the original Rimar.gr, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (9.9 sec) belongs to the original domain Rimar.gr.

Page Optimization Overview & Recommendations

Page size can be reduced by 350.4 kB (56%)

Content Size

629.0 kB

After Optimization

278.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rimar.gr main page is 629.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 485.7 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 3.9 kB

  • Original 6.1 kB
  • After minification 5.9 kB
  • After compression 2.3 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 3.9 kB or 63% of the original size.

Image Optimization

-3%

Potential reduce by 3.3 kB

  • Original 122.6 kB
  • After minification 119.3 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. RIMAR images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 332.4 kB

  • Original 485.7 kB
  • After minification 483.9 kB
  • After compression 153.3 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 332.4 kB or 68% of the original size.

CSS Optimization

-74%

Potential reduce by 10.8 kB

  • Original 14.5 kB
  • After minification 14.0 kB
  • After compression 3.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. Rimar.gr needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 74% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rimar.gr

rimar.gr

770 ms

reset.css

reset.css

298 ms

style.css

style.css

466 ms

index.css

index.css

468 ms

jquery.js

jquery.js

625 ms

x5engine.js

x5engine.js

470 ms

x5cart.js

x5cart.js

9935 ms

kitchen-welcome.jpg

kitchen-welcome.jpg

770 ms

greece.png

greece.png

157 ms

united-kingdom.png

united-kingdom.png

149 ms

ga.js

ga.js

9 ms

swfobject.js

swfobject.js

294 ms

x5engine.deferrable.js

x5engine.deferrable.js

732 ms

l10n.js

l10n.js

298 ms

x5cartengine.js

x5cartengine.js

302 ms

x5settings.js

x5settings.js

303 ms

__utm.gif

__utm.gif

18 ms

collect

collect

65 ms

ga-audiences

ga-audiences

38 ms

hor_main.png

hor_main.png

295 ms

hor_main_h.png

hor_main_h.png

296 ms

hor_main_c.png

hor_main_c.png

297 ms

hor_main_f.png

hor_main_f.png

302 ms

hor_main_f_h.png

hor_main_f_h.png

314 ms

hor_main_f_c.png

hor_main_f_c.png

313 ms

hor_main_m.png

hor_main_m.png

439 ms

hor_main_m_h.png

hor_main_m_h.png

443 ms

hor_main_m_c.png

hor_main_m_c.png

444 ms

hor_main_l.png

hor_main_l.png

450 ms

hor_main_l_h.png

hor_main_l_h.png

467 ms

hor_main_l_c.png

hor_main_l_c.png

468 ms

sub.png

sub.png

596 ms

sub_h.png

sub_h.png

597 ms

sub_f.png

sub_f.png

597 ms

sub_m.png

sub_m.png

599 ms

sub_l.png

sub_l.png

622 ms

sub_f_h.png

sub_f_h.png

623 ms

sub_m_h.png

sub_m_h.png

740 ms

sub_l_h.png

sub_l_h.png

743 ms

imLoad.gif

imLoad.gif

744 ms

imClose.png

imClose.png

749 ms

print.css

print.css

151 ms

Accessibility Review

rimar.gr accessibility score

79

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

Links do not have a discernible name

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

rimar.gr 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

rimar.gr SEO score

83

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rimar.gr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Rimar.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

rimar.gr

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