Access vortez.net. Vortez - Computer Hardware News & Reviews

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

www.vortez.net

447 ms

reset.css

87 ms

main-stylesheet.css

206 ms

lightbox.css

190 ms

shortcode.css

197 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 78% of them (84 requests) were addressed to the original Vortez.net, 6% (6 requests) were made to I.ytimg.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Vortez.net.

Content Size

3.8 MB

After Optimization

1.6 MB

In fact, the total size of Vortez.net main page is 3.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. 65% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 64.6 kB

Original 75.7 kB
After minification 63.6 kB
After compression 11.1 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 12.1 kB, which is 16% 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 64.6 kB or 85% of the original size.

Image Optimization

-53%

Potential reduce by 1.5 MB

Original 2.8 MB
After minification 1.3 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, Vortez needs image optimization as it can save up to 1.5 MB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 357.5 kB

Original 534.8 kB
After minification 489.9 kB
After compression 177.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 357.5 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 334.8 kB

Original 401.2 kB
After minification 377.9 kB
After compression 66.4 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. Vortez.net needs all CSS files to be minified and compressed as it can save up to 334.8 kB or 83% of the original size.

Requests Now

100

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

High

robots.txt is not valid

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

EN
Encoding

ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vortez.net 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 Vortez.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

vortez.net

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Vortez - Computer Hardware News & Reviews

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.vortez.net

reset.css

main-stylesheet.css

lightbox.css

shortcode.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.vortez.net

reset.css

main-stylesheet.css

lightbox.css

shortcode.css

font-awesome.min.css

colors.css

contentteller.php

menu_style.css

jquery.js

jquery.validationEngine-en.js

jquery.validationEngine.js

front-subscribers.js

jquery-latest.min.js

lightbox.js

cookieconsent.min.js

orange-themes-responsive.js

theme-scripts.js

css

css

analytics.js

collect

hqdefault.jpg

background-1.jpg

close.png

loading.gif

prev.png

next.png

WEB-TEST-03.png

search.png

newsletter.png

px.gif

1267

1266

1264

1265

1261

1260

rssfeed.gif

3554

3553

3552

3551