Tools & Wizards About Us

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

perpetuum.ro

Mocheta, covor PVC, linoleum, perdele si draperii hotel | Perpetuum

Page Load Speed

8.1 sec in total

First Response

379 ms

Resources Loaded

7.2 sec

Page Rendered

545 ms

About Website

Welcome to perpetuum.ro homepage info - get ready to check Perpetuum best content for Romania right away, or after learning these important things about perpetuum.ro

Importator si distribuitor de mocheta, covor PVC, linoleum si alte pardoseli profesionale. Productie, montaj si distributie textile pt hotel: perdele, draperii, prosoape, halate de baie, lenjerii de p...

Visit perpetuum.ro

Key Findings

We analyzed Perpetuum.ro page load time and found that the first response time was 379 ms and then it took 7.7 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

perpetuum.ro performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value3,740 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value31.3 s

0/100

10%

Network Requests Diagram

perpetuum.ro

379 ms

www.perpetuum.ro

876 ms

calendar-win2k-1.css

115 ms

widgets.css

228 ms

style.css

342 ms

Our browser made a total of 263 requests to load all elements on the main page. We found that 80% of them (211 requests) were addressed to the original Perpetuum.ro, 4% (10 requests) were made to Youtube.com and 2% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Carpetyourlife.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.6 MB (31%)

Content Size

8.4 MB

After Optimization

5.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Perpetuum.ro main page is 8.4 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. Only a small number of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 154.8 kB

  • Original 180.0 kB
  • After minification 180.0 kB
  • After compression 25.2 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 154.8 kB or 86% of the original size.

Image Optimization

-25%

Potential reduce by 1.7 MB

  • Original 6.6 MB
  • After minification 4.9 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. Obviously, Perpetuum needs image optimization as it can save up to 1.7 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-50%

Potential reduce by 752.5 kB

  • Original 1.5 MB
  • After minification 1.3 MB
  • After compression 747.2 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 752.5 kB or 50% of the original size.

CSS Optimization

-11%

Potential reduce by 16.7 kB

  • Original 148.0 kB
  • After minification 147.7 kB
  • After compression 131.2 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. Perpetuum.ro needs all CSS files to be minified and compressed as it can save up to 16.7 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (31%)

Requests Now

249

After Optimization

173

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

perpetuum.ro accessibility score

63

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

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

perpetuum.ro best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

perpetuum.ro SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    RO

  • Language Claimed

    RO

  • Encoding

    UTF-8

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