Tools & Wizards About Us
publi-line.be screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

publi-line.be

Home

Page Load Speed

3.6 sec in total

First Response

284 ms

Resources Loaded

3.2 sec

Page Rendered

150 ms

publi-line.be screenshot

About Website

Welcome to publi-line.be homepage info - get ready to check Publi Line best content for Belgium right away, or after learning these important things about publi-line.be

Surprise your entourage by offering a gift that makes sense among over 30,000 unique items! Free quote online. Increase your visibility. Powerbank, tote bags, magnetic car holder, pens, mugs, jute ......

Visit publi-line.be

Key Findings

We analyzed Publi-line.be page load time and found that the first response time was 284 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

publi-line.be performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value22.5 s

0/100

10%

TBT (Total Blocking Time)

Value13,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.325

35/100

15%

TTI (Time to Interactive)

Value23.5 s

1/100

10%

Network Requests Diagram

publi-line.be

284 ms

694 ms

widgetkit-f6d04eb4.css

250 ms

rokbox.css

247 ms

grid-12.css

170 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 96% of them (51 requests) were addressed to the original Publi-line.be, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (766 ms) belongs to the original domain Publi-line.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 686.0 kB (59%)

Content Size

1.2 MB

After Optimization

471.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Publi-line.be main page is 1.2 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. 35% of websites need less resources to load. Javascripts take 700.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 28.3 kB

  • Original 34.1 kB
  • After minification 24.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 9.2 kB, which is 27% 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 28.3 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 3.4 kB

  • Original 216.5 kB
  • After minification 213.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. Publi Line images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 487.0 kB

  • Original 700.0 kB
  • After minification 692.6 kB
  • After compression 213.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 487.0 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 167.3 kB

  • Original 207.3 kB
  • After minification 192.3 kB
  • After compression 40.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. Publi-line.be needs all CSS files to be minified and compressed as it can save up to 167.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (65%)

Requests Now

51

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

publi-line.be

publi-line.be

284 ms

694 ms

widgetkit-f6d04eb4.css

widgetkit-f6d04eb4.css

250 ms

rokbox.css

rokbox.css

247 ms

grid-12.css

grid-12.css

170 ms

gantry.css

gantry.css

168 ms

joomla.css

joomla.css

256 ms

joomla-ie7.css

joomla-ie7.css

213 ms

joomla.css

joomla.css

253 ms

style8.css

style8.css

272 ms

extensions.css

extensions.css

299 ms

demo-styles.css

demo-styles.css

328 ms

template.css

template.css

332 ms

template-ie7.css

template-ie7.css

336 ms

typography.css

typography.css

344 ms

fusionmenu.css

fusionmenu.css

357 ms

nsb.css

nsb.css

386 ms

template.css

template.css

412 ms

mootools-core.js

mootools-core.js

591 ms

core.js

core.js

431 ms

caption.js

caption.js

426 ms

jquery.js

jquery.js

615 ms

widgetkit-b4b38745.js

widgetkit-b4b38745.js

470 ms

mootools-more.js

mootools-more.js

766 ms

rokbox.js

rokbox.js

638 ms

gantry-smartload.js

gantry-smartload.js

515 ms

gantry-inputs.js

gantry-inputs.js

556 ms

browser-engines.js

browser-engines.js

612 ms

ie7-fixes.js

ie7-fixes.js

666 ms

fusion.js

fusion.js

675 ms

lightbox.js

lightbox.js

99 ms

mediaelement-and-player.js

mediaelement-and-player.js

306 ms

spotlight.js

spotlight.js

100 ms

analytics.js

analytics.js

132 ms

slideshow.js

slideshow.js

184 ms

header-gradient.png

header-gradient.png

111 ms

shadow-divider.png

shadow-divider.png

113 ms

logo.png

logo.png

250 ms

fr.gif

fr.gif

116 ms

nl.gif

nl.gif

114 ms

header-bg.png

header-bg.png

225 ms

topdaddy.png

topdaddy.png

201 ms

black-overlay.png

black-overlay.png

203 ms

divider-line2.png

divider-line2.png

204 ms

publi-line.jpg

publi-line.jpg

544 ms

boutique-publi-line.jpg

boutique-publi-line.jpg

309 ms

marques-publi-line.jpg

marques-publi-line.jpg

399 ms

produits-publi-line-home.jpg

produits-publi-line-home.jpg

390 ms

contact-publi-line-home.jpg

contact-publi-line-home.jpg

321 ms

facebook_log_32.png

facebook_log_32.png

348 ms

linkedin_log_32.png

linkedin_log_32.png

415 ms

collect

collect

17 ms

publi-line-communication.jpg

publi-line-communication.jpg

563 ms

Accessibility Review

publi-line.be accessibility score

65

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

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

publi-line.be best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

publi-line.be SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Publi-line.be 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 French language. Our system also found out that Publi-line.be 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

publi-line.be

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