Tools & Wizards About Us
im-arch.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

im-arch.com

Italian IM-ARCH 2019 goes to Asia: Discover More...

Page Load Speed

8.9 sec in total

First Response

3.1 sec

Resources Loaded

5.4 sec

Page Rendered

374 ms

im-arch.com screenshot

About Website

Welcome to im-arch.com homepage info - get ready to check IM ARCH best content for Italy right away, or after learning these important things about im-arch.com

Don't miss the opportunity to join the first IM-ARCH event on VR/AR in Singapore: three days of workshops, talks, networking, live experience, Italian Food and Prosecco. Discover main topics, spe...

Visit im-arch.com

Key Findings

We analyzed Im-arch.com page load time and found that the first response time was 3.1 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

im-arch.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

im-arch.com

3115 ms

wp-emoji-release.min.js

316 ms

front.min.css

313 ms

settings.css

317 ms

magnific.css

317 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 91% of them (105 requests) were addressed to the original Im-arch.com, 3% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Im-arch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 197.4 kB (11%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Im-arch.com main page is 1.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. 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 56.0 kB

  • Original 70.3 kB
  • After minification 67.5 kB
  • After compression 14.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 56.0 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 118.6 kB

  • Original 1.1 MB
  • After minification 1.0 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, IM ARCH needs image optimization as it can save up to 118.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 13.6 kB

  • Original 459.6 kB
  • After minification 459.4 kB
  • After compression 446.0 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

-5%

Potential reduce by 9.2 kB

  • Original 180.3 kB
  • After minification 179.9 kB
  • After compression 171.1 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. Im-arch.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 84 (78%)

Requests Now

108

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

im-arch.com

im-arch.com

3115 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

316 ms

front.min.css

front.min.css

313 ms

settings.css

settings.css

317 ms

magnific.css

magnific.css

317 ms

wp-matterport.css

wp-matterport.css

316 ms

tt-widget.css

tt-widget.css

329 ms

superfish.css

superfish.css

409 ms

style.css

style.css

409 ms

event_template.css

event_template.css

410 ms

responsive.css

responsive.css

411 ms

css

css

20 ms

style.css

style.css

410 ms

modules.min.css

modules.min.css

642 ms

style_dynamic.css

style_dynamic.css

502 ms

modules-responsive.min.css

modules-responsive.min.css

504 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

505 ms

style.css

style.css

506 ms

font-awesome.min.css

font-awesome.min.css

507 ms

style.min.css

style.min.css

599 ms

ionicons.min.css

ionicons.min.css

600 ms

style.css

style.css

602 ms

simple-line-icons.css

simple-line-icons.css

604 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

623 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

710 ms

css

css

21 ms

js_composer.min.css

js_composer.min.css

812 ms

jquery.js

jquery.js

810 ms

jquery-migrate.min.js

jquery-migrate.min.js

711 ms

front.min.js

front.min.js

727 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

754 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

911 ms

magnific.min.js

magnific.min.js

850 ms

wp-matterport.js

wp-matterport.js

850 ms

jQueryPlugins.min.js

jQueryPlugins.min.js

857 ms

scripts.js

scripts.js

914 ms

css

css

20 ms

formreset.min.css

formreset.min.css

945 ms

formsmain.min.css

formsmain.min.css

944 ms

readyclass.min.css

readyclass.min.css

963 ms

js

js

41 ms

browsers.min.css

browsers.min.css

656 ms

jquery.json.min.js

jquery.json.min.js

701 ms

gravityforms.min.js

gravityforms.min.js

702 ms

language-selector.js

language-selector.js

699 ms

core.min.js

core.min.js

706 ms

widget.min.js

widget.min.js

731 ms

tabs.min.js

tabs.min.js

657 ms

jquery.ba-bbq.min.js

jquery.ba-bbq.min.js

713 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

704 ms

timetable.js

timetable.js

716 ms

accordion.min.js

accordion.min.js

716 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

757 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

662 ms

jquery.appear.js

jquery.appear.js

713 ms

modernizr.min.js

modernizr.min.js

713 ms

hoverIntent.min.js

hoverIntent.min.js

727 ms

jquery.plugin.js

jquery.plugin.js

621 ms

owl.carousel.min.js

owl.carousel.min.js

712 ms

waypoints.min.js

waypoints.min.js

710 ms

Chart.min.js

Chart.min.js

808 ms

fluidvids.min.js

fluidvids.min.js

698 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

677 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

648 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

666 ms

parallax.min.js

parallax.min.js

695 ms

jquery.waitforimages.js

jquery.waitforimages.js

669 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

618 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

619 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

632 ms

jquery.countdown.min.js

jquery.countdown.min.js

672 ms

counter.js

counter.js

667 ms

absoluteCounter.min.js

absoluteCounter.min.js

610 ms

analytics.js

analytics.js

50 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

580 ms

jquery.parallax-scroll.js

jquery.parallax-scroll.js

620 ms

easypiechart.js

easypiechart.js

627 ms

jquery.multiscroll.min.js

jquery.multiscroll.min.js

658 ms

collect

collect

21 ms

modules.min.js

modules.min.js

616 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

18 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

19 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

19 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

20 ms

wp-embed.min.js

wp-embed.min.js

627 ms

sitepress.js

sitepress.js

627 ms

js_composer_front.min.js

js_composer_front.min.js

646 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

668 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

768 ms

Logo-Sito-Web-Im-Arch.png

Logo-Sito-Web-Im-Arch.png

682 ms

logo_white.png

logo_white.png

634 ms

CHINA001.jpg

CHINA001.jpg

806 ms

theViewer-Discovery-FG-1.png

theViewer-Discovery-FG-1.png

640 ms

Epic-games.png

Epic-games.png

704 ms

VR-Global.png

VR-Global.png

716 ms

Constructive-Labs.png

Constructive-Labs.png

729 ms

Neiko.jpg

Neiko.jpg

677 ms

tangram.png

tangram.png

706 ms

Vive_MainLogoRGB_Black-2.png

Vive_MainLogoRGB_Black-2.png

701 ms

3dws.png

3dws.png

676 ms

Whitelable.png

Whitelable.png

798 ms

MADI.jpg

MADI.jpg

708 ms

MDE.png

MDE.png

719 ms

d2-conference.png

d2-conference.png

719 ms

treddi-1.png

treddi-1.png

691 ms

RenderIT.png

RenderIT.png

717 ms

Officina.jpg

Officina.jpg

702 ms

Exibart.png

Exibart.png

717 ms

IUAV.png

IUAV.png

737 ms

Background-Counter.jpg

Background-Counter.jpg

851 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

495 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

507 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

518 ms

revolution.extension.parallax.min.js

revolution.extension.parallax.min.js

542 ms

ElegantIcons.woff

ElegantIcons.woff

623 ms

Accessibility Review

im-arch.com accessibility score

92

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

High

Some elements have a [tabindex] value greater than 0

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

Links do not have a discernible name

Best Practices

im-arch.com 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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

im-arch.com SEO score

86

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Im-arch.com 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 Im-arch.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

im-arch.com

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