Tools & Wizards About Us
holoforge.io screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% 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

  • 89

    SEO

    Google-friendlier than
    66% of websites

holoforge.io

Mixed Reality | HoloForge, video game expertise for professionals

Page Load Speed

4.3 sec in total

First Response

235 ms

Resources Loaded

3.8 sec

Page Rendered

254 ms

holoforge.io screenshot

About Website

Visit holoforge.io now to see the best up-to-date Holo Forge content and also check out these interesting facts you probably never knew about holoforge.io

As an augmented reality agency, HoloForge designs mixed reality applications to boost your company through its digital transformation.

Visit holoforge.io

Key Findings

We analyzed Holoforge.io page load time and found that the first response time was 235 ms and then it took 4 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

holoforge.io performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

95/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

holoforge.io

235 ms

1345 ms

dnd-upload-cf7.css

164 ms

styles.css

238 ms

front.min.css

247 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 63% of them (36 requests) were addressed to the original Holoforge.io, 32% (18 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Holoforge.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 152.4 kB (17%)

Content Size

899.2 kB

After Optimization

746.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Holoforge.io main page is 899.2 kB. 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. Javascripts take 375.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 143.2 kB

  • Original 173.0 kB
  • After minification 172.1 kB
  • After compression 29.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. 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 143.2 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 5.7 kB

  • Original 318.1 kB
  • After minification 312.4 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. Holo Forge images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 375.1 kB
  • After minification 375.1 kB
  • After compression 373.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

-4%

Potential reduce by 1.4 kB

  • Original 33.0 kB
  • After minification 32.5 kB
  • After compression 31.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. Holoforge.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (81%)

Requests Now

36

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Holo Forge. 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

holoforge.io

holoforge.io

235 ms

1345 ms

dnd-upload-cf7.css

dnd-upload-cf7.css

164 ms

styles.css

styles.css

238 ms

front.min.css

front.min.css

247 ms

style.min.css

style.min.css

243 ms

style.min.css

style.min.css

248 ms

dsefreestyles.css

dsefreestyles.css

251 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

249 ms

custom-forms.css

custom-forms.css

318 ms

style.css

style.css

320 ms

front.min.js

front.min.js

326 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

406 ms

et-divi-customizer-global.min.css

et-divi-customizer-global.min.css

329 ms

js

js

50 ms

inspector.js

inspector.js

328 ms

hooks.min.js

hooks.min.js

395 ms

i18n.min.js

i18n.min.js

396 ms

index.js

index.js

404 ms

index.js

index.js

568 ms

codedropz-uploader-min.js

codedropz-uploader-min.js

568 ms

jquery.min.js

jquery.min.js

572 ms

jquery-migrate.min.js

jquery-migrate.min.js

569 ms

scripts.min.js

scripts.min.js

659 ms

jquery.fitvids.js

jquery.fitvids.js

569 ms

frontend-bundle.min.js

frontend-bundle.min.js

570 ms

common.js

common.js

570 ms

api.js

api.js

63 ms

wp-polyfill.min.js

wp-polyfill.min.js

645 ms

index.js

index.js

577 ms

defree_scripts.js

defree_scripts.js

577 ms

Logo_HoloForge_ByAsobowhite_Plan-de-travail-1.png

Logo_HoloForge_ByAsobowhite_Plan-de-travail-1.png

445 ms

Logo_HoloForge_ByAsobowhite_Plan-de-travail-1-1.png

Logo_HoloForge_ByAsobowhite_Plan-de-travail-1-1.png

139 ms

MicrosoftTeams-image-28-scaled-1-1080x675.jpg

MicrosoftTeams-image-28-scaled-1-1080x675.jpg

353 ms

AFPIA-1080x675.jpg

AFPIA-1080x675.jpg

291 ms

Matrix-1080x675.jpg

Matrix-1080x675.jpg

449 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

38 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

43 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

42 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

43 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

44 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

45 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff

67 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

45 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

44 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff

70 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

70 ms

modules.woff

modules.woff

249 ms

recaptcha__en.js

recaptcha__en.js

39 ms

style.min.css

style.min.css

86 ms

Accessibility Review

holoforge.io 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

Links do not have a discernible name

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

holoforge.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

holoforge.io SEO score

89

Search Engine Optimization Advices

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 Holoforge.io 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 Holoforge.io 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

holoforge.io

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