Tools & Wizards About Us
octilus.pt screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

octilus.pt

octilus.pt

Page Load Speed

3 sec in total

First Response

387 ms

Resources Loaded

2.5 sec

Page Rendered

198 ms

octilus.pt screenshot

About Website

Click here to check amazing Octilus content for Portugal. Otherwise, check out these important facts you probably never knew about octilus.pt

This domain may be for sale!

Visit octilus.pt

Key Findings

We analyzed Octilus.pt page load time and found that the first response time was 387 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

octilus.pt performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.298

40/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

octilus.pt

387 ms

8521dc288a24ccac1b07da9c06926c57_1443612724.css

258 ms

jquery.js

256 ms

prototype.js

272 ms

ccard.js

172 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 78% of them (75 requests) were addressed to the original Octilus.pt, 10% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Octilus.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 673.5 kB (42%)

Content Size

1.6 MB

After Optimization

944.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Octilus.pt main page is 1.6 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. Images take 782.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 71.1 kB

  • Original 87.9 kB
  • After minification 82.2 kB
  • After compression 16.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 71.1 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 22.9 kB

  • Original 782.5 kB
  • After minification 759.6 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. Octilus images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 436.6 kB

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

CSS Optimization

-85%

Potential reduce by 142.9 kB

  • Original 167.8 kB
  • After minification 135.0 kB
  • After compression 25.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. Octilus.pt needs all CSS files to be minified and compressed as it can save up to 142.9 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

95

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

octilus.pt

octilus.pt

387 ms

8521dc288a24ccac1b07da9c06926c57_1443612724.css

8521dc288a24ccac1b07da9c06926c57_1443612724.css

258 ms

jquery.js

jquery.js

256 ms

prototype.js

prototype.js

272 ms

ccard.js

ccard.js

172 ms

validation.js

validation.js

174 ms

builder.js

builder.js

176 ms

effects.js

effects.js

267 ms

dragdrop.js

dragdrop.js

281 ms

controls.js

controls.js

283 ms

slider.js

slider.js

336 ms

js.js

js.js

339 ms

form.js

form.js

343 ms

script.js

script.js

345 ms

translate.js

translate.js

344 ms

cookies.js

cookies.js

348 ms

jquery.jqtransform.js

jquery.jqtransform.js

420 ms

functions.js

functions.js

429 ms

jquery.hover.intent.js

jquery.hover.intent.js

423 ms

instorepickup.js

instorepickup.js

426 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

429 ms

jquery.slider.js

jquery.slider.js

434 ms

efects.js

efects.js

504 ms

on4u.js

on4u.js

508 ms

respond.min.js

respond.min.js

511 ms

matchMedia.js

matchMedia.js

515 ms

menu1.css

menu1.css

513 ms

mobile.css

mobile.css

524 ms

ga.js

ga.js

30 ms

pt.gif

pt.gif

92 ms

logo_octilus_pt.png

logo_octilus_pt.png

89 ms

banner_PT_becool_blue3_1105.jpg

banner_PT_becool_blue3_1105.jpg

263 ms

banner_SPT_2_PT_1105.jpg

banner_SPT_2_PT_1105.jpg

265 ms

banner_PT_becool_new_1105.jpg

banner_PT_becool_new_1105.jpg

342 ms

soportes_pt.jpg

soportes_pt.jpg

340 ms

I6_pt.jpg

I6_pt.jpg

520 ms

SPT-SSP-LG099.jpg

SPT-SSP-LG099.jpg

186 ms

throbber.gif

throbber.gif

275 ms

SST-BQ023.jpg

SST-BQ023.jpg

350 ms

TPU-BQ023-WOO3.jpg

TPU-BQ023-WOO3.jpg

351 ms

SGP11415-1.jpg

SGP11415-1.jpg

363 ms

SGP11139-1.jpg

SGP11139-1.jpg

424 ms

samsung-grand-prime.jpg

samsung-grand-prime.jpg

426 ms

13030005g-1.jpg

13030005g-1.jpg

436 ms

BXMCB3226200C02-1.jpg

BXMCB3226200C02-1.jpg

438 ms

MUSKI0423-1.jpg

MUSKI0423-1.jpg

451 ms

_amazon_galaxy_s3_mini_steinheil_film_1.jpg

_amazon_galaxy_s3_mini_steinheil_film_1.jpg

509 ms

banner_1.png

banner_1.png

511 ms

banner_2.png

banner_2.png

521 ms

banner_3.png

banner_3.png

525 ms

banner_4.png

banner_4.png

539 ms

banner_5.png

banner_5.png

594 ms

Mail.png

Mail.png

595 ms

Phone.png

Phone.png

602 ms

Facebook.png

Facebook.png

606 ms

Google.png

Google.png

612 ms

Twitter.png

Twitter.png

626 ms

Blogger.png

Blogger.png

679 ms

Pinterest.png

Pinterest.png

679 ms

Tumblr.png

Tumblr.png

686 ms

Linked.png

Linked.png

692 ms

YouTube.png

YouTube.png

701 ms

banner_footer_face2_ptbr.png

banner_footer_face2_ptbr.png

715 ms

cart_icon.png

cart_icon.png

759 ms

toplinksap.png

toplinksap.png

748 ms

__utm.gif

__utm.gif

18 ms

1134 ms

slide-point2.png

slide-point2.png

693 ms

likebox.php

likebox.php

185 ms

slide-point.png

slide-point.png

607 ms

controls-sprite-prev.png

controls-sprite-prev.png

546 ms

controls-sprite-next.png

controls-sprite-next.png

592 ms

prev-horizontal.png

prev-horizontal.png

582 ms

n7IAcY2jJIh.css

n7IAcY2jJIh.css

281 ms

n--mLoVmLJM.css

n--mLoVmLJM.css

349 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

644 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

614 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

484 ms

TTCre3391I0.js

TTCre3391I0.js

485 ms

next-horizontal.png

next-horizontal.png

530 ms

li-arr.png

li-arr.png

541 ms

12208595_10153089423006020_5404279686884759078_n.jpg

12208595_10153089423006020_5404279686884759078_n.jpg

278 ms

12079450_10153024318961020_1330175905610885030_n.png

12079450_10153024318961020_1330175905610885030_n.png

345 ms

12715713_1537028443262334_1266655564116682726_n.jpg

12715713_1537028443262334_1266655564116682726_n.jpg

411 ms

485374_951839181518812_241262181080254868_n.jpg

485374_951839181518812_241262181080254868_n.jpg

478 ms

12743510_1063775740334882_5499110089558137773_n.jpg

12743510_1063775740334882_5499110089558137773_n.jpg

479 ms

12662523_156513544725601_4309161515991950931_n.jpg

12662523_156513544725601_4309161515991950931_n.jpg

481 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

71 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

71 ms

btn-cart.png

btn-cart.png

91 ms

item_avisame.png

item_avisame.png

88 ms

197885e43d044736a88d460d6eb139f4_1354201816.css

197885e43d044736a88d460d6eb139f4_1354201816.css

90 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

71 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

134 ms

nr-852.min.js

nr-852.min.js

16 ms

d81ec33e68

d81ec33e68

52 ms

Accessibility Review

octilus.pt accessibility score

86

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

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

SEO Factors

octilus.pt SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

octilus.pt

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