Tools & Wizards About Us
fortecho.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

fortecho.com

World's Leading Art Security & Asset Monitoring Solutions

Page Load Speed

5.9 sec in total

First Response

234 ms

Resources Loaded

3.8 sec

Page Rendered

1.9 sec

fortecho.com screenshot

About Website

Visit fortecho.com now to see the best up-to-date Fortecho content and also check out these interesting facts you probably never knew about fortecho.com

State-of-the-art, wireless asset monitoring for artwork and other valuable assets. Protect them with confidence with Fortecho's top security products. Find out more.

Visit fortecho.com

Key Findings

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

fortecho.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value3,070 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

fortecho.com

234 ms

fortecho.com

628 ms

c2a09bf6cc1863b9cf44e046593f11a3.css

207 ms

c2fa388fd64032e4ffa2788372c90908.css

314 ms

912aa9f75ad512403ea9cd561c8c4353.css

422 ms

Our browser made a total of 151 requests to load all elements on the main page. We found that 86% of them (130 requests) were addressed to the original Fortecho.com, 4% (6 requests) were made to Use.typekit.net and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Fortecho.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 367.6 kB (15%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fortecho.com main page is 2.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. 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 225.9 kB

  • Original 264.9 kB
  • After minification 264.4 kB
  • After compression 39.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 225.9 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 46.5 kB

  • Original 1.4 MB
  • After minification 1.3 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. Fortecho images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 37.1 kB

  • Original 533.2 kB
  • After minification 532.8 kB
  • After compression 496.2 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

-21%

Potential reduce by 58.1 kB

  • Original 274.2 kB
  • After minification 274.2 kB
  • After compression 216.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. Fortecho.com needs all CSS files to be minified and compressed as it can save up to 58.1 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 85 (61%)

Requests Now

139

After Optimization

54

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fortecho.com

fortecho.com

234 ms

fortecho.com

fortecho.com

628 ms

c2a09bf6cc1863b9cf44e046593f11a3.css

c2a09bf6cc1863b9cf44e046593f11a3.css

207 ms

c2fa388fd64032e4ffa2788372c90908.css

c2fa388fd64032e4ffa2788372c90908.css

314 ms

912aa9f75ad512403ea9cd561c8c4353.css

912aa9f75ad512403ea9cd561c8c4353.css

422 ms

13894e5b65d0d25007fe32bacc59bee2.css

13894e5b65d0d25007fe32bacc59bee2.css

314 ms

ude3crl.css

ude3crl.css

111 ms

a5bddf6001b5872514bf7535070ae8ea.css

a5bddf6001b5872514bf7535070ae8ea.css

429 ms

0de3528fb3e4fbd693419195d43a0d10.css

0de3528fb3e4fbd693419195d43a0d10.css

317 ms

726499742170e98cba3937abcee8238f.css

726499742170e98cba3937abcee8238f.css

415 ms

d6d575c3fb967eab2c3f46ff106acdc7.css

d6d575c3fb967eab2c3f46ff106acdc7.css

418 ms

a43c58813cb2c898a64770e6c44d301b.css

a43c58813cb2c898a64770e6c44d301b.css

522 ms

3a77d891899e98cadd8507b155ea6aef.css

3a77d891899e98cadd8507b155ea6aef.css

433 ms

7e40203a6aac983e2446d33ea8a28269.css

7e40203a6aac983e2446d33ea8a28269.css

518 ms

91520de8d17f1f1b6e083897620a90da.css

91520de8d17f1f1b6e083897620a90da.css

630 ms

fd16c6f02d3335f122e951db5114888a.css

fd16c6f02d3335f122e951db5114888a.css

530 ms

a7554a5e89ca7254138a75ddcbb7e5b5.css

a7554a5e89ca7254138a75ddcbb7e5b5.css

531 ms

f72f22c7377ba67d122ba3dd2d744310.css

f72f22c7377ba67d122ba3dd2d744310.css

740 ms

47dac90ca7ee845f16949308a8cf2b0d.css

47dac90ca7ee845f16949308a8cf2b0d.css

622 ms

8ca8d24f44970ae316d8583504101b89.css

8ca8d24f44970ae316d8583504101b89.css

626 ms

98a731e57a903092597fb463d3ac7f95.css

98a731e57a903092597fb463d3ac7f95.css

638 ms

483accd23e0d5002b962f849ff223afc.css

483accd23e0d5002b962f849ff223afc.css

640 ms

ca6fc4134b1ed375216aba5b14a38bc3.css

ca6fc4134b1ed375216aba5b14a38bc3.css

728 ms

e561e486c016c76e618d789d50067deb.css

e561e486c016c76e618d789d50067deb.css

734 ms

d6f6ac175cfb58c18807ce45982f00e9.css

d6f6ac175cfb58c18807ce45982f00e9.css

732 ms

d13ff5a0b7957bf7530dd08bedeae61f.css

d13ff5a0b7957bf7530dd08bedeae61f.css

752 ms

3caffb0fa3e936fb299f81cbf7dbb25a.css

3caffb0fa3e936fb299f81cbf7dbb25a.css

754 ms

d3a90d456f92f948102401d3c219df65.css

d3a90d456f92f948102401d3c219df65.css

832 ms

jquery.min.js

jquery.min.js

842 ms

jquery-migrate.min.js

jquery-migrate.min.js

839 ms

allow-webp-image-public.js

allow-webp-image-public.js

853 ms

front.min.js

front.min.js

852 ms

14980.js

14980.js

55 ms

js

js

68 ms

js

js

121 ms

25843472.js

25843472.js

432 ms

c80bc3a97a83a87d24b50f79f228a7cc.css

c80bc3a97a83a87d24b50f79f228a7cc.css

859 ms

cbd5aea37072b2156e4431d1950db1cd.css

cbd5aea37072b2156e4431d1950db1cd.css

973 ms

981db42e5a43934e8e0d1651bce98d08.css

981db42e5a43934e8e0d1651bce98d08.css

974 ms

9909186ff0e980b8e6716a3bb738adf0.css

9909186ff0e980b8e6716a3bb738adf0.css

974 ms

dynamic-conditions-public.js

dynamic-conditions-public.js

975 ms

api.js

api.js

37 ms

imagesloaded.min.js

imagesloaded.min.js

885 ms

p.css

p.css

26 ms

theme.min.js

theme.min.js

779 ms

drop-down-mobile-menu.min.js

drop-down-mobile-menu.min.js

780 ms

drop-down-search.min.js

drop-down-search.min.js

778 ms

magnific-popup.min.js

magnific-popup.min.js

778 ms

ow-lightbox.min.js

ow-lightbox.min.js

775 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

677 ms

ow-slider.min.js

ow-slider.min.js

674 ms

scroll-effect.min.js

scroll-effect.min.js

723 ms

scroll-top.min.js

scroll-top.min.js

727 ms

select.min.js

select.min.js

728 ms

flickr.min.js

flickr.min.js

644 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

642 ms

hoverIntent.min.js

hoverIntent.min.js

644 ms

make-column-clickable.js

make-column-clickable.js

728 ms

jquery-numerator.min.js

jquery-numerator.min.js

640 ms

slick.min.js

slick.min.js

637 ms

jquery.jsticky.min.js

jquery.jsticky.min.js

631 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

639 ms

webpack.runtime.min.js

webpack.runtime.min.js

639 ms

frontend-modules.min.js

frontend-modules.min.js

637 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

633 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

672 ms

wp-polyfill.min.js

wp-polyfill.min.js

657 ms

hooks.min.js

hooks.min.js

656 ms

i18n.min.js

i18n.min.js

655 ms

frontend.min.js

frontend.min.js

630 ms

waypoints.min.js

waypoints.min.js

633 ms

core.min.js

core.min.js

623 ms

gtm.js

gtm.js

70 ms

frontend.min.js

frontend.min.js

616 ms

elements-handlers.min.js

elements-handlers.min.js

627 ms

leadflows.js

leadflows.js

518 ms

banner.js

banner.js

470 ms

collectedforms.js

collectedforms.js

459 ms

25843472.js

25843472.js

465 ms

jet-blocks.min.js

jet-blocks.min.js

570 ms

d

d

53 ms

d

d

57 ms

d

d

53 ms

jet-elements.min.js

jet-elements.min.js

597 ms

anime.min.js

anime.min.js

601 ms

jet-popup-frontend.js

jet-popup-frontend.js

602 ms

jet-tabs-frontend.min.js

jet-tabs-frontend.min.js

604 ms

frontend.min.js

frontend.min.js

616 ms

fa-solid-900.woff

fa-solid-900.woff

836 ms

d

d

16 ms

d

d

15 ms

fa-solid-900.ttf

fa-solid-900.ttf

1003 ms

fa-regular-400.ttf

fa-regular-400.ttf

699 ms

fa-brands-400.woff

fa-brands-400.woff

729 ms

fa-brands-400.ttf

fa-brands-400.ttf

809 ms

hero_fallback-1.webp

hero_fallback-1.webp

847 ms

GlamorousNastyGartersnake-size_restricted.gif

GlamorousNastyGartersnake-size_restricted.gif

793 ms

MH-awards-381x400.png

MH-awards-381x400.png

743 ms

shutterstock_316493525-600x400.jpg

shutterstock_316493525-600x400.jpg

780 ms

Guardian-424x400.jpg

Guardian-424x400.jpg

844 ms

Olympia-600x400.jpg

Olympia-600x400.jpg

845 ms

Automatic-Signal-600x400.jpg

Automatic-Signal-600x400.jpg

839 ms

MH-512x400.png

MH-512x400.png

850 ms

UKRG-Corporate-Member-logo.png

UKRG-Corporate-Member-logo.png

766 ms

Sydney-Modern-Project_I-600x400.jpg

Sydney-Modern-Project_I-600x400.jpg

861 ms

recaptcha__en.js

recaptcha__en.js

21 ms

shutterstock_1931787956-600x400.jpg

shutterstock_1931787956-600x400.jpg

859 ms

LAD_2-600x400.jpg

LAD_2-600x400.jpg

859 ms

Private-Art-Collection-France-Villa-blur-600x400.jpg

Private-Art-Collection-France-Villa-blur-600x400.jpg

861 ms

Private-Collection_London-600x400.jpg

Private-Collection_London-600x400.jpg

858 ms

Data-Centre-600x400.jpg

Data-Centre-600x400.jpg

833 ms

Cadogan-Tate-1.jpg

Cadogan-Tate-1.jpg

819 ms

Henry-Bath-600x400.jpg

Henry-Bath-600x400.jpg

825 ms

Warwick-Castle-1-600x400.jpg

Warwick-Castle-1-600x400.jpg

831 ms

Wexner-Center-for-the-Arts-600x400.jpg

Wexner-Center-for-the-Arts-600x400.jpg

836 ms

Waddesdon-Corner-1-600x400.jpg

Waddesdon-Corner-1-600x400.jpg

839 ms

Hermitage-front-1-600x400.jpg

Hermitage-front-1-600x400.jpg

832 ms

3-1.webp

3-1.webp

961 ms

national_gallery.png

national_gallery.png

864 ms

National-Gallery-Australia.png

National-Gallery-Australia.png

867 ms

gallery.png

gallery.png

864 ms

National-Gallery-Oslo-1.png

National-Gallery-Oslo-1.png

863 ms

Getty-Museum-Los-Angles.png

Getty-Museum-Los-Angles.png

831 ms

dubai.png

dubai.png

864 ms

reunion.png

reunion.png

869 ms

egypt.png

egypt.png

878 ms

Vancouver-Art-Gallery.png

Vancouver-Art-Gallery.png

840 ms

AIC-red-997-x-662.png

AIC-red-997-x-662.png

695 ms

Guggenheim-Bilbao.png

Guggenheim-Bilbao.png

722 ms

british_museum.png

british_museum.png

671 ms

Logos28-2.png

Logos28-2.png

663 ms

bt.png

bt.png

672 ms

HSBC-1.png

HSBC-1.png

633 ms

Louis-Vuitton.png

Louis-Vuitton.png

678 ms

Logos16-1.png

Logos16-1.png

695 ms

bishop_auckland.jpg

bishop_auckland.jpg

651 ms

Logos48-1.png

Logos48-1.png

656 ms

heritage.png

heritage.png

671 ms

quote-background.png

quote-background.png

655 ms

Xray-Fortecho.webp

Xray-Fortecho.webp

698 ms

about-us-map.jpg

about-us-map.jpg

639 ms

iy0euzq5

iy0euzq5

68 ms

Fortecho-solutions.png

Fortecho-solutions.png

108 ms

Fortecho-ARTS-White-on-transparent-v.webp

Fortecho-ARTS-White-on-transparent-v.webp

111 ms

Fortecho-LITE-Below-White-on-Transparent-2-768x766-1.webp

Fortecho-LITE-Below-White-on-Transparent-2-768x766-1.webp

108 ms

FORTECHO-Marine.webp

FORTECHO-Marine.webp

111 ms

FORTECHO-Industry.webp

FORTECHO-Industry.webp

113 ms

Fortecho-LUXE-2020-Logo.png

Fortecho-LUXE-2020-Logo.png

110 ms

quote-1.png

quote-1.png

211 ms

frame.a60ea367.js

frame.a60ea367.js

24 ms

vendor.989ae25f.js

vendor.989ae25f.js

47 ms

Accessibility Review

fortecho.com accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

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

fortecho.com best practices score

92

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

Page has valid source maps

SEO Factors

fortecho.com SEO score

81

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

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 Fortecho.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 Fortecho.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

fortecho.com

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