Tools & Wizards About Us
oblio.eu screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

oblio.eu

Oblio: Programul de Facturare + Stocuri | GRATUIT 1 AN !

Page Load Speed

8 sec in total

First Response

1.4 sec

Resources Loaded

5.4 sec

Page Rendered

1.2 sec

oblio.eu screenshot

About Website

Welcome to oblio.eu homepage info - get ready to check Oblio best content for Romania right away, or after learning these important things about oblio.eu

Oblio este programul de facturare si gestiune stocuri iubit de utilizatorii sai. Creat de experti contabili, iubit de cunoscatori, venerat de incepatori. Integrat cu Saga, WinMentor, Ciel. Peste 40.00...

Visit oblio.eu

Key Findings

We analyzed Oblio.eu page load time and found that the first response time was 1.4 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

oblio.eu performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

www.oblio.eu

1423 ms

uc.js

66 ms

343_utils.js

602 ms

all.min.css

744 ms

purpose.css

1264 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 88% of them (50 requests) were addressed to the original Oblio.eu, 4% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Oblio.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.6 kB (73%)

Content Size

240.5 kB

After Optimization

63.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Oblio.eu main page is 240.5 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. 55% of websites need less resources to load. Javascripts take 113.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 76.4 kB

  • Original 93.8 kB
  • After minification 70.8 kB
  • After compression 17.4 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 23.0 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 76.4 kB or 81% of the original size.

Image Optimization

-37%

Potential reduce by 12.4 kB

  • Original 33.5 kB
  • After minification 21.1 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. Obviously, Oblio needs image optimization as it can save up to 12.4 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 87.9 kB

  • Original 113.2 kB
  • After minification 113.2 kB
  • After compression 25.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 87.9 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (30%)

Requests Now

50

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.oblio.eu

www.oblio.eu

1423 ms

uc.js

uc.js

66 ms

343_utils.js

343_utils.js

602 ms

all.min.css

all.min.css

744 ms

purpose.css

purpose.css

1264 ms

purpose.core.js

purpose.core.js

1013 ms

343_jqutils.js

343_jqutils.js

515 ms

language.js

language.js

717 ms

js

js

50 ms

swiper.min.css

swiper.min.css

294 ms

swiper.min.js

swiper.min.js

610 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

424 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

486 ms

purpose.js

purpose.js

517 ms

css

css

34 ms

gtm.js

gtm.js

194 ms

fbevents.js

fbevents.js

221 ms

logo-white.webp

logo-white.webp

280 ms

video_new.webp

video_new.webp

762 ms

synevo.png

synevo.png

418 ms

glovo.png

glovo.png

408 ms

hilton-garden-inn.png

hilton-garden-inn.png

541 ms

macbook.svg

macbook.svg

414 ms

iphonex.svg

iphonex.svg

334 ms

screen-phone-1.webp

screen-phone-1.webp

575 ms

testimonial.webp

testimonial.webp

782 ms

audit-logos.webp

audit-logos.webp

542 ms

stack-reports.webp

stack-reports.webp

676 ms

cool-2.webp

cool-2.webp

921 ms

rb5.webp

rb5.webp

920 ms

rb2.webp

rb2.webp

934 ms

rb_pareri.webp

rb_pareri.webp

934 ms

rb4.webp

rb4.webp

882 ms

rb3.webp

rb3.webp

908 ms

rb1.webp

rb1.webp

1005 ms

macbook.webp

macbook.webp

1157 ms

business-card-mockup.webp

business-card-mockup.webp

1049 ms

produse.webp

produse.webp

1052 ms

panou-stradal.webp

panou-stradal.webp

1056 ms

pliant.webp

pliant.webp

1064 ms

people-faces.webp

people-faces.webp

1131 ms

devices.webp

devices.webp

1179 ms

fact-1.webp

fact-1.webp

1180 ms

fact-2.svg

fact-2.svg

1176 ms

fact-3.svg

fact-3.svg

1195 ms

fact-4.svg

fact-4.svg

1254 ms

logo-full-white.webp

logo-full-white.webp

1283 ms

contact_oblio.png

contact_oblio.png

1300 ms

pwa-light.svg

pwa-light.svg

1307 ms

font

font

138 ms

fa-solid-900.woff

fa-solid-900.woff

1278 ms

fa-regular-400.woff

fa-regular-400.woff

1424 ms

fa-light-300.woff

fa-light-300.woff

1317 ms

fa-brands-400.woff

fa-brands-400.woff

1373 ms

openwidget.js

openwidget.js

74 ms

fa-light-300.ttf

fa-light-300.ttf

417 ms

fa-light-300.svg

fa-light-300.svg

131 ms

Accessibility Review

oblio.eu accessibility score

83

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

oblio.eu best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

oblio.eu SEO score

95

Search Engine Optimization Advices

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 Oblio.eu 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 Oblio.eu 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

oblio.eu

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