Tools & Wizards About Us
indinor.pt screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

indinor.pt

Indinor - Indústrias Químicas S.A. | Porto, Trofa, Portugal

Page Load Speed

4.3 sec in total

First Response

366 ms

Resources Loaded

3.2 sec

Page Rendered

802 ms

indinor.pt screenshot

About Website

Welcome to indinor.pt homepage info - get ready to check Indinor best content right away, or after learning these important things about indinor.pt

A Indinor foi fundada em 1987 e dedica-se ao fabrico e comercialização de produtos químicos para as indústrias de curtumes e calçado. Para além disso fabrica para terceiros produtos químicos para outr...

Visit indinor.pt

Key Findings

We analyzed Indinor.pt page load time and found that the first response time was 366 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

indinor.pt performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

Network Requests Diagram

indinor.pt

366 ms

indinor.pt

1416 ms

front.min.css

95 ms

dashicons.min.css

275 ms

to-top-public.css

273 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 68% of them (56 requests) were addressed to the original Indinor.pt, 11% (9 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to C.tile.openstreetmap.org. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Indinor.pt.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

961.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indinor.pt main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 457.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 106.3 kB

  • Original 131.9 kB
  • After minification 128.3 kB
  • After compression 25.6 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 106.3 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 2.6 kB

  • Original 389.7 kB
  • After minification 387.1 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. Indinor images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 457.2 kB
  • After minification 457.2 kB
  • After compression 454.5 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

-3%

Potential reduce by 2.5 kB

  • Original 96.6 kB
  • After minification 95.9 kB
  • After compression 94.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. Indinor.pt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 51 (72%)

Requests Now

71

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indinor.pt

indinor.pt

366 ms

indinor.pt

indinor.pt

1416 ms

front.min.css

front.min.css

95 ms

dashicons.min.css

dashicons.min.css

275 ms

to-top-public.css

to-top-public.css

273 ms

leaflet.css

leaflet.css

270 ms

leaflet.responsive.popup.css

leaflet.responsive.popup.css

271 ms

leaflet-gesture-handling.css

leaflet-gesture-handling.css

269 ms

leaflet.fullscreen.css

leaflet.fullscreen.css

272 ms

wp_mapit.css

wp_mapit.css

363 ms

style.min.css

style.min.css

364 ms

theme.min.css

theme.min.css

366 ms

header-footer.min.css

header-footer.min.css

368 ms

frontend-lite.min.css

frontend-lite.min.css

459 ms

post-5.css

post-5.css

368 ms

swiper.min.css

swiper.min.css

465 ms

frontend-lite.min.css

frontend-lite.min.css

464 ms

global.css

global.css

467 ms

post-17.css

post-17.css

468 ms

post-11.css

post-11.css

468 ms

post-133.css

post-133.css

554 ms

style.css

style.css

556 ms

css

css

39 ms

front.min.js

front.min.js

553 ms

jquery.min.js

jquery.min.js

650 ms

jquery-migrate.min.js

jquery-migrate.min.js

560 ms

to-top-public.js

to-top-public.js

561 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

668 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

648 ms

widget-icon-list.min.css

widget-icon-list.min.css

666 ms

language-switcher.min.css

language-switcher.min.css

720 ms

animations.min.css

animations.min.css

721 ms

leaflet.js

leaflet.js

837 ms

leaflet.responsive.popup.js

leaflet.responsive.popup.js

746 ms

leaflet-gesture-handling.js

leaflet-gesture-handling.js

745 ms

Leaflet.fullscreen.min.js

Leaflet.fullscreen.min.js

745 ms

wp_mapit.js

wp_mapit.js

761 ms

wp_mapit_multipin.js

wp_mapit_multipin.js

761 ms

api.js

api.js

40 ms

hello-frontend.min.js

hello-frontend.min.js

848 ms

jquery.sticky.min.js

jquery.sticky.min.js

763 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

587 ms

lottie.min.js

lottie.min.js

762 ms

imagesloaded.min.js

imagesloaded.min.js

594 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

667 ms

webpack.runtime.min.js

webpack.runtime.min.js

669 ms

frontend-modules.min.js

frontend-modules.min.js

771 ms

hooks.min.js

hooks.min.js

580 ms

i18n.min.js

i18n.min.js

595 ms

frontend.min.js

frontend.min.js

678 ms

waypoints.min.js

waypoints.min.js

677 ms

core.min.js

core.min.js

678 ms

frontend.min.js

frontend.min.js

593 ms

elements-handlers.min.js

elements-handlers.min.js

663 ms

logo.png

logo.png

475 ms

logos2.png

logos2.png

479 ms

534-e1710520038363.jpg

534-e1710520038363.jpg

545 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

20 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

34 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

56 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

64 ms

recaptcha__en.js

recaptcha__en.js

28 ms

382.png

382.png

35 ms

383.png

383.png

40 ms

382.png

382.png

49 ms

382.png

382.png

36 ms

382.png

382.png

38 ms

383.png

383.png

35 ms

383.png

383.png

39 ms

383.png

383.png

53 ms

382.png

382.png

48 ms

383.png

383.png

49 ms

maps-and-flags.png

maps-and-flags.png

113 ms

383.png

383.png

33 ms

383.png

383.png

32 ms

382.png

382.png

34 ms

382.png

382.png

38 ms

Accessibility Review

indinor.pt accessibility score

88

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.

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 IDs are not unique

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

indinor.pt 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

indinor.pt SEO score

95

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indinor.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Indinor.pt 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

indinor.pt

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