Tools & Wizards About Us
toledo.be screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    54% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

toledo.be

Telecom solution providers for the business world | IP Nexia

Page Load Speed

4.2 sec in total

First Response

356 ms

Resources Loaded

3.5 sec

Page Rendered

318 ms

toledo.be screenshot

About Website

Click here to check amazing Toledo content for Belgium. Otherwise, check out these important facts you probably never knew about toledo.be

IP Nexia aims to work with you to provide unified telecommunication solutions that help you deliver efficient services. Contact us for more information.

Visit toledo.be

Key Findings

We analyzed Toledo.be page load time and found that the first response time was 356 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

toledo.be performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

toledo.be

356 ms

toledo.be

355 ms

www.ipnexia.com

653 ms

king-hosting.css

87 ms

reset.css

172 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Toledo.be, 81% (112 requests) were made to Ipnexia.com and 12% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Ipnexia.com.

Page Optimization Overview & Recommendations

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

Content Size

4.3 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Toledo.be main page is 4.3 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.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 119.6 kB

  • Original 148.5 kB
  • After minification 141.8 kB
  • After compression 29.0 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 119.6 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 47.0 kB

  • Original 2.3 MB
  • After minification 2.2 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. Toledo images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 439.6 kB

  • Original 630.3 kB
  • After minification 588.6 kB
  • After compression 190.7 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 439.6 kB or 70% of the original size.

CSS Optimization

-87%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 161.0 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. Toledo.be needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (58%)

Requests Now

99

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

toledo.be

toledo.be

356 ms

toledo.be

toledo.be

355 ms

www.ipnexia.com

www.ipnexia.com

653 ms

king-hosting.css

king-hosting.css

87 ms

reset.css

reset.css

172 ms

bootstrap.min.css

bootstrap.min.css

425 ms

style.css

style.css

338 ms

animate.css

animate.css

430 ms

king.css

king.css

426 ms

arkahost.css

arkahost.css

594 ms

shortcodes.css

shortcodes.css

341 ms

box-shortcodes.css

box-shortcodes.css

422 ms

cubeportfolio.min.css

cubeportfolio.min.css

429 ms

owl.transitions.css

owl.transitions.css

505 ms

owl.carousel.css

owl.carousel.css

506 ms

loopslider.css

loopslider.css

506 ms

tabacc.css

tabacc.css

507 ms

detached.css

detached.css

511 ms

reslider.css

reslider.css

587 ms

css

css

38 ms

menu-3.css

menu-3.css

589 ms

style.min.css

style.min.css

587 ms

js_composer.min.css

js_composer.min.css

1265 ms

styles.css

styles.css

597 ms

settings.css

settings.css

668 ms

cms-navigation-base.css

cms-navigation-base.css

670 ms

cms-navigation.css

cms-navigation.css

671 ms

custom.css

custom.css

671 ms

responsive.css

responsive.css

677 ms

responsive-tabs.css

responsive-tabs.css

750 ms

responsive-portfolio.css

responsive-portfolio.css

752 ms

jquery.min.js

jquery.min.js

838 ms

jquery-migrate.min.js

jquery-migrate.min.js

754 ms

king.user.js

king.user.js

760 ms

script.min.js

script.min.js

834 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

918 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

922 ms

jq-sticky-anything.min.js

jq-sticky-anything.min.js

845 ms

js

js

58 ms

cookieconsent.min.css

cookieconsent.min.css

30 ms

cookieconsent.min.js

cookieconsent.min.js

40 ms

king.hosting.js

king.hosting.js

913 ms

owl.carousel.js

owl.carousel.js

916 ms

modal.js

modal.js

855 ms

custom.js

custom.js

840 ms

font-awesome.min.css

font-awesome.min.css

674 ms

simple-line-icons.css

simple-line-icons.css

671 ms

etlinefont.css

etlinefont.css

595 ms

king.user.js

king.user.js

598 ms

smoothscroll.js

smoothscroll.js

667 ms

viewportchecker.js

viewportchecker.js

665 ms

jquery.cubeportfolio.min.js

jquery.cubeportfolio.min.js

668 ms

main.js

main.js

596 ms

custom.js

custom.js

603 ms

js_composer_front.min.js

js_composer_front.min.js

671 ms

stickThis.js

stickThis.js

672 ms

shortcode.js

shortcode.js

673 ms

core.min.js

core.min.js

597 ms

tabs.min.js

tabs.min.js

604 ms

jquery-ui-tabs-rotate.min.js

jquery-ui-tabs-rotate.min.js

669 ms

gtm.js

gtm.js

63 ms

ipnexia-logo-2.png

ipnexia-logo-2.png

290 ms

menu-vline.png

menu-vline.png

127 ms

ipnexia-slider-1.jpg

ipnexia-slider-1.jpg

286 ms

solutions-ipnexia.png

solutions-ipnexia.png

135 ms

why-us-ipnexia-4.jpg

why-us-ipnexia-4.jpg

136 ms

police-polbruno.jpg

police-polbruno.jpg

189 ms

dun-bradstreet.jpg

dun-bradstreet.jpg

223 ms

partena.jpg

partena.jpg

222 ms

greenpeece.jpg

greenpeece.jpg

223 ms

groupon.jpg

groupon.jpg

225 ms

Mundolab.png

Mundolab.png

135 ms

keyrus-biopharma.jpg

keyrus-biopharma.jpg

226 ms

crisis-group.jpg

crisis-group.jpg

335 ms

therabel.jpg

therabel.jpg

336 ms

Bit4You.png

Bit4You.png

153 ms

mercuri-urval.jpg

mercuri-urval.jpg

335 ms

BXLLaique.jpg

BXLLaique.jpg

225 ms

securitas-logo-1.jpg

securitas-logo-1.jpg

336 ms

cirpack.jpg

cirpack.jpg

337 ms

verizon.jpg

verizon.jpg

337 ms

atlance.jpg

atlance.jpg

399 ms

colt-logo.jpg

colt-logo.jpg

406 ms

verixi-logo.jpg

verixi-logo.jpg

405 ms

proximus.jpg

proximus.jpg

406 ms

bt-logo.jpg

bt-logo.jpg

406 ms

datacenter-1.jpg

datacenter-1.jpg

406 ms

telenet-logo.jpg

telenet-logo.jpg

436 ms

eurofiber.jpg

eurofiber.jpg

486 ms

ipnexia-logo-footer-1.png

ipnexia-logo-footer-1.png

638 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

73 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

111 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

132 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

135 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

136 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

134 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

134 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

134 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

135 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

136 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

136 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

314 ms

footer-img1.png

footer-img1.png

160 ms

footer-bg-graph.png

footer-bg-graph.png

375 ms

scroll-top-arrow.png

scroll-top-arrow.png

243 ms

analytics.js

analytics.js

61 ms

police-polbruno.jpg

police-polbruno.jpg

152 ms

collect

collect

21 ms

partena.jpg

partena.jpg

119 ms

dun-bradstreet.jpg

dun-bradstreet.jpg

186 ms

greenpeece.jpg

greenpeece.jpg

185 ms

collect

collect

110 ms

groupon.jpg

groupon.jpg

183 ms

keyrus-biopharma.jpg

keyrus-biopharma.jpg

182 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

232 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

233 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

229 ms

ga-audiences

ga-audiences

130 ms

crisis-group.jpg

crisis-group.jpg

153 ms

therabel.jpg

therabel.jpg

222 ms

mercuri-urval.jpg

mercuri-urval.jpg

235 ms

securitas-logo-1.jpg

securitas-logo-1.jpg

236 ms

cirpack.jpg

cirpack.jpg

237 ms

verizon.jpg

verizon.jpg

235 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

14 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

14 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

14 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

14 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

13 ms

up-arrow-e.png

up-arrow-e.png

248 ms

atlance.jpg

atlance.jpg

255 ms

verixi-logo.jpg

verixi-logo.jpg

252 ms

datacenter-1.jpg

datacenter-1.jpg

254 ms

proximus.jpg

proximus.jpg

253 ms

bt-logo.jpg

bt-logo.jpg

321 ms

colt-logo.jpg

colt-logo.jpg

320 ms

telenet-logo.jpg

telenet-logo.jpg

301 ms

eurofiber.jpg

eurofiber.jpg

254 ms

loader.gif

loader.gif

215 ms

Accessibility Review

toledo.be accessibility score

77

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

Image elements do not have [alt] attributes

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

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

toledo.be 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

toledo.be SEO score

77

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toledo.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Toledo.be 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

toledo.be

Open Graph data is detected on the main page of Toledo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: