Tools & Wizards About Us
istorm.ro screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

istorm.ro

iStorm - Software & Web Development, Romania

Page Load Speed

4.1 sec in total

First Response

439 ms

Resources Loaded

3.3 sec

Page Rendered

347 ms

istorm.ro screenshot

About Website

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

iStorm - Software and Web development company, Creative solutions for your business

Visit istorm.ro

Key Findings

We analyzed Istorm.ro page load time and found that the first response time was 439 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

istorm.ro performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

istorm.ro

439 ms

istorm.ro

458 ms

www.istorm.ro

792 ms

bootstrap.min.css

334 ms

jquery.fancybox-v=2.1.5.css

338 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 70% of them (49 requests) were addressed to the original Istorm.ro, 10% (7 requests) were made to Fonts.gstatic.com and 9% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Istorm.ro.

Page Optimization Overview & Recommendations

Page size can be reduced by 251.2 kB (20%)

Content Size

1.2 MB

After Optimization

994.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Istorm.ro main page is 1.2 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. 60% of websites need less resources to load. Images take 778.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 22.8 kB

  • Original 28.6 kB
  • After minification 22.1 kB
  • After compression 5.8 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 6.5 kB, which is 23% 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 22.8 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 29.5 kB

  • Original 778.6 kB
  • After minification 749.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. IStorm images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 96.5 kB

  • Original 316.1 kB
  • After minification 311.2 kB
  • After compression 219.6 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 96.5 kB or 31% of the original size.

CSS Optimization

-84%

Potential reduce by 102.3 kB

  • Original 121.9 kB
  • After minification 101.8 kB
  • After compression 19.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. Istorm.ro needs all CSS files to be minified and compressed as it can save up to 102.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (32%)

Requests Now

57

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

istorm.ro

istorm.ro

439 ms

istorm.ro

istorm.ro

458 ms

www.istorm.ro

www.istorm.ro

792 ms

bootstrap.min.css

bootstrap.min.css

334 ms

jquery.fancybox-v=2.1.5.css

jquery.fancybox-v=2.1.5.css

338 ms

font-awesome.min.css

font-awesome.min.css

447 ms

style.css

style.css

339 ms

css

css

30 ms

css

css

48 ms

logo-blue.png

logo-blue.png

339 ms

s02.png

s02.png

339 ms

s01.png

s01.png

457 ms

s03.png

s03.png

546 ms

fo.jpg

fo.jpg

464 ms

it.jpg

it.jpg

463 ms

cs.jpg

cs.jpg

459 ms

rp.jpg

rp.jpg

458 ms

tr.jpg

tr.jpg

459 ms

mc.jpg

mc.jpg

564 ms

cl.jpg

cl.jpg

569 ms

plusone.js

plusone.js

18 ms

html5shiv.js

html5shiv.js

574 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

681 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

578 ms

bootstrap.min.js

bootstrap.min.js

584 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

679 ms

script.js

script.js

679 ms

ghita.jpg

ghita.jpg

711 ms

silviu.jpg

silviu.jpg

710 ms

marius.jpg

marius.jpg

711 ms

sim.jpg

sim.jpg

902 ms

gabor.jpg

gabor.jpg

846 ms

stefan.jpg

stefan.jpg

794 ms

wali.jpg

wali.jpg

849 ms

cristina.jpg

cristina.jpg

849 ms

edi.jpg

edi.jpg

849 ms

vlad.jpg

vlad.jpg

905 ms

florin.jpg

florin.jpg

909 ms

you_2.png

you_2.png

958 ms

astazi.jpg

astazi.jpg

959 ms

ep.gif

ep.gif

968 ms

ts.png

ts.png

1013 ms

test-me-logo.png

test-me-logo.png

792 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

92 ms

website-arrows.png

website-arrows.png

687 ms

NaPecZTIAOhVxoMyOr9n_E7fdM3mCA.ttf

NaPecZTIAOhVxoMyOr9n_E7fdM3mCA.ttf

26 ms

NaPDcZTIAOhVxoMyOr9n_E7ffGjEGIVzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffGjEGIVzZg.ttf

33 ms

NaPDcZTIAOhVxoMyOr9n_E7ffAzHGIVzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffAzHGIVzZg.ttf

42 ms

NaPDcZTIAOhVxoMyOr9n_E7ffBzCGIVzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffBzCGIVzZg.ttf

49 ms

fontawesome-webfont-v=3.2.1.woff

fontawesome-webfont-v=3.2.1.woff

634 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

49 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

49 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

49 ms

analytics.js

analytics.js

31 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

12 ms

fastbutton

fastbutton

16 ms

fo.jpg

fo.jpg

362 ms

it.jpg

it.jpg

371 ms

cs.jpg

cs.jpg

417 ms

rp.jpg

rp.jpg

420 ms

tr.jpg

tr.jpg

436 ms

mc.jpg

mc.jpg

474 ms

cl.jpg

cl.jpg

475 ms

postmessageRelay

postmessageRelay

66 ms

collect

collect

12 ms

js

js

51 ms

developers.google.com

developers.google.com

817 ms

3192416480-postmessagerelay.js

3192416480-postmessagerelay.js

65 ms

rpc:shindig_random.js

rpc:shindig_random.js

7 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

Accessibility Review

istorm.ro accessibility score

51

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

<frame> or <iframe> elements do not have a title

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

istorm.ro best practices score

58

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

istorm.ro SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Istorm.ro can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Istorm.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

istorm.ro

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