Tools & Wizards About Us

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

gnex.ro

gnex.ro

Page Load Speed

11.9 sec in total

First Response

470 ms

Resources Loaded

9.3 sec

Page Rendered

2.2 sec

About Website

Visit gnex.ro now to see the best up-to-date Gnex content for Romania and also check out these interesting facts you probably never knew about gnex.ro

gnex.ro

Visit gnex.ro

Key Findings

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

gnex.ro performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

gnex.ro

470 ms

gnex.ro

1431 ms

webfont.js

19 ms

bootstrap.min.css

349 ms

font-awesome.min.css

359 ms

Our browser made a total of 207 requests to load all elements on the main page. We found that 97% of them (200 requests) were addressed to the original Gnex.ro, 1% (3 requests) were made to Fonts.gstatic.com and 0% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Gnex.ro.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (12%)

Content Size

13.5 MB

After Optimization

11.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gnex.ro main page is 13.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.9 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 1.2 MB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 100.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. This page needs HTML code to be minified as it can gain 170.1 kB, which is 13% 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 1.2 MB or 92% of the original size.

Image Optimization

-4%

Potential reduce by 434.1 kB

  • Original 11.9 MB
  • After minification 11.5 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. Gnex images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 12.2 kB

  • Original 224.0 kB
  • After minification 224.0 kB
  • After compression 211.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 1.6 kB

  • Original 62.2 kB
  • After minification 61.9 kB
  • After compression 60.6 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. Gnex.ro has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (13%)

Requests Now

200

After Optimization

174

  • Images
  • JavaScript
  • CSS

The browser has sent 200 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gnex. 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 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

gnex.ro 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

Form elements do not have associated labels

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

gnex.ro best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

gnex.ro SEO score

84

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

High

robots.txt is not valid

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 Gnex.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 Gnex.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 data is detected on the main page of Gnex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: