Tools & Wizards About Us
occar.int screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

occar.int

OCCAR - Home

Page Load Speed

5.2 sec in total

First Response

257 ms

Resources Loaded

4.6 sec

Page Rendered

311 ms

occar.int screenshot

About Website

Welcome to occar.int homepage info - get ready to check OCCAR best content for Italy right away, or after learning these important things about occar.int

ORGANISATION FOR JOINT ARMAMENT COOPERATION facilitates and manages complex, cooperative defence equipment programmes to the satisfaction of its customers.

Visit occar.int

Key Findings

We analyzed Occar.int page load time and found that the first response time was 257 ms and then it took 5 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

occar.int performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

occar.int

257 ms

occar.int

1427 ms

jquery.min.js

230 ms

material.min.css

447 ms

semantic.css

960 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 87% of them (40 requests) were addressed to the original Occar.int, 11% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Occar.int.

Page Optimization Overview & Recommendations

Page size can be reduced by 960.6 kB (41%)

Content Size

2.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Occar.int 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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 109.8 kB

  • Original 136.5 kB
  • After minification 136.3 kB
  • After compression 26.7 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 109.8 kB or 80% of the original size.

Image Optimization

-37%

Potential reduce by 552.0 kB

  • Original 1.5 MB
  • After minification 928.7 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. Obviously, OCCAR needs image optimization as it can save up to 552.0 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 172.6 kB

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

CSS Optimization

-45%

Potential reduce by 126.2 kB

  • Original 282.8 kB
  • After minification 282.7 kB
  • After compression 156.5 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. Occar.int needs all CSS files to be minified and compressed as it can save up to 126.2 kB or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (71%)

Requests Now

35

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

occar.int

occar.int

257 ms

occar.int

occar.int

1427 ms

jquery.min.js

jquery.min.js

230 ms

material.min.css

material.min.css

447 ms

semantic.css

semantic.css

960 ms

_icons.css

_icons.css

363 ms

material.min.js

material.min.js

468 ms

StyleSheet.css

StyleSheet.css

367 ms

base.css

base.css

367 ms

custom_topbar.css

custom_topbar.css

471 ms

light-bottom.css

light-bottom.css

465 ms

custom_content.css

custom_content.css

468 ms

box.css

box.css

551 ms

animate.css

animate.css

616 ms

simplelightbox.css

simplelightbox.css

591 ms

WebResource.axd

WebResource.axd

557 ms

ScriptResource.axd

ScriptResource.axd

574 ms

ScriptResource.axd

ScriptResource.axd

749 ms

ScriptResource.axd

ScriptResource.axd

738 ms

semantic.js

semantic.js

1259 ms

bootstrap335.min.js

bootstrap335.min.js

738 ms

jquery-ui.min.js

jquery-ui.min.js

1080 ms

base.js

base.js

846 ms

topbar.js

topbar.js

848 ms

cookieconsent.min.js

cookieconsent.min.js

855 ms

box.js

box.js

1039 ms

simple-lightbox.min.js

simple-lightbox.min.js

944 ms

css2

css2

27 ms

ionicons.min.css

ionicons.min.css

105 ms

resources%2Ftemplates%2F12%2FlogotGwIO111922.png

resources%2Ftemplates%2F12%2FlogotGwIO111922.png

249 ms

logo.png

logo.png

249 ms

1_IMG-20240829-HYDEF%20MDR%20Meeting%20(002)_.jpg

1_IMG-20240829-HYDEF%20MDR%20Meeting%20(002)_.jpg

251 ms

1_FREMM%20EVO%201_.jpg

1_FREMM%20EVO%201_.jpg

319 ms

1_HYDIS_Image_Ground_scenario_.jpg

1_HYDIS_Image_Ground_scenario_.jpg

251 ms

tuev.png

tuev.png

454 ms

bg_vid.png

bg_vid.png

1750 ms

resourcessite1General%C3%9Esign%0Bg_vid.png

resourcessite1General%C3%9Esign%0Bg_vid.png

337 ms

embl_occar.png

embl_occar.png

337 ms

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbouRckg.ttf

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbouRckg.ttf

202 ms

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbsWRckg.ttf

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbsWRckg.ttf

318 ms

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbl6Wckg.ttf

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbl6Wckg.ttf

318 ms

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbmyWckg.ttf

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbmyWckg.ttf

338 ms

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbjKWckg.ttf

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbjKWckg.ttf

337 ms

ionicons.ttf

ionicons.ttf

376 ms

fontello.woff

fontello.woff

286 ms

fontello.ttf

fontello.ttf

101 ms

Accessibility Review

occar.int accessibility score

82

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 input fields do not have accessible names

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

occar.int 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

Missing source maps for large first-party JavaScript

SEO Factors

occar.int SEO score

91

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

occar.int

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