Tools & Wizards About Us

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

iweb.com

Leaseweb | Infrastructure as a Service (IaaS) & Cloud

Page Load Speed

3.6 sec in total

First Response

260 ms

Resources Loaded

2.4 sec

Page Rendered

867 ms

About Website

Click here to check amazing Iweb content for Syrian Arab Republic. Otherwise, check out these important facts you probably never knew about iweb.com

Leaseweb is an Infrastructure-as-a-Service (IaaS) provider that offers Dedicated Servers, CDN, and Cloud Hosting solutions in a worldwide network.

Visit iweb.com

Key Findings

We analyzed Iweb.com page load time and found that the first response time was 260 ms and then it took 3.3 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

iweb.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value19.7 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value3,550 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

iweb.com

260 ms

iweb.com

395 ms

www.leaseweb.com

122 ms

adyen.css

464 ms

adyen.js

841 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Iweb.com, 86% (59 requests) were made to Leaseweb.com and 3% (2 requests) were made to Checkoutshopper-live.adyen.com. The less responsive or slowest element that took the longest time to load (841 ms) relates to the external source Checkoutshopper-live.adyen.com.

Page Optimization Overview & Recommendations

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

Content Size

3.4 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 108.3 kB

  • Original 131.5 kB
  • After minification 121.8 kB
  • After compression 23.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 108.3 kB or 82% of the original size.

Image Optimization

-16%

Potential reduce by 389.7 kB

  • Original 2.4 MB
  • After minification 2.1 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, Iweb needs image optimization as it can save up to 389.7 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 150.6 kB

  • Original 293.5 kB
  • After minification 267.0 kB
  • After compression 142.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 150.6 kB or 51% of the original size.

CSS Optimization

-77%

Potential reduce by 394.1 kB

  • Original 513.9 kB
  • After minification 506.6 kB
  • After compression 119.8 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. Iweb.com needs all CSS files to be minified and compressed as it can save up to 394.1 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

iweb.com accessibility score

80

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

iweb.com 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

iweb.com SEO score

85

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

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

    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 Iweb.com 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 Iweb.com 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 Iweb. 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: