Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

exponor.com

EXPONOR | Conheça o nosso recinto e os nossos eventos

Page Load Speed

2.6 sec in total

First Response

260 ms

Resources Loaded

1.7 sec

Page Rendered

598 ms

exponor.com screenshot

About Website

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

Descubra na Exponor as instalações e os serviços adequados para receber o seu evento. Consulte as nossas feiras e eventos!

Visit exponor.com

Key Findings

We analyzed Exponor.com page load time and found that the first response time was 260 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

exponor.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

exponor.pt

260 ms

exponor.pt

439 ms

styles.css

98 ms

css

46 ms

logo_exPONOR.svg

194 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Exponor.com, 13% (1 request) were made to Fonts.googleapis.com and 13% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (810 ms) relates to the external source Exponor.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.0 kB (12%)

Content Size

300.6 kB

After Optimization

263.6 kB

In fact, the total size of Exponor.com main page is 300.6 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. Only 5% of websites need less resources to load. Images take 297.2 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 1.3 kB

  • Original 1.9 kB
  • After minification 1.3 kB
  • After compression 608 B

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. This page needs HTML code to be minified as it can gain 579 B, which is 31% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.3 kB or 67% of the original size.

Image Optimization

-12%

Potential reduce by 35.5 kB

  • Original 297.2 kB
  • After minification 261.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, EXPONOR needs image optimization as it can save up to 35.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-19%

Potential reduce by 299 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 1.3 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. Exponor.com needs all CSS files to be minified and compressed as it can save up to 299 B or 19% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EXPONOR. According to our analytics all requests are already optimized.

Accessibility Review

exponor.com accessibility score

71

Accessibility Issues

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

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

SEO Factors

exponor.com SEO score

100

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

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exponor.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Exponor.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

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