Tools & Wizards About Us
1407.be screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

1407.be

Endgültige Einstellung der 1407.be | Proximus

Page Load Speed

4.2 sec in total

First Response

308 ms

Resources Loaded

3.7 sec

Page Rendered

200 ms

1407.be screenshot

About Website

Click here to check amazing 1407 content for Belgium. Otherwise, check out these important facts you probably never knew about 1407.be

L'annuaire 1307 vous permet de trouver rapidement un numéro de téléphone ou une adresse sur des entreprises et des particuliers en Belgique !

Visit 1407.be

Key Findings

We analyzed 1407.be page load time and found that the first response time was 308 ms and then it took 3.9 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

1407.be performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value9,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.561

12/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

1407.be

308 ms

www.1307.be

1233 ms

system.base.css

185 ms

system.menus.css

182 ms

system.messages.css

181 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 1407.be, 61% (60 requests) were made to 1307.be and 15% (15 requests) were made to S1.2mdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source 1307.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 740.1 kB (65%)

Content Size

1.1 MB

After Optimization

403.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1407.be 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. 55% of websites need less resources to load. Javascripts take 761.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 29.0 kB

  • Original 37.6 kB
  • After minification 34.7 kB
  • After compression 8.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 29.0 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 10.4 kB

  • Original 130.2 kB
  • After minification 119.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. 1407 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 525.2 kB

  • Original 761.4 kB
  • After minification 658.4 kB
  • After compression 236.2 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 525.2 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 175.4 kB

  • Original 214.7 kB
  • After minification 173.0 kB
  • After compression 39.2 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. 1407.be needs all CSS files to be minified and compressed as it can save up to 175.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (69%)

Requests Now

96

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1407.be

1407.be

308 ms

www.1307.be

www.1307.be

1233 ms

system.base.css

system.base.css

185 ms

system.menus.css

system.menus.css

182 ms

system.messages.css

system.messages.css

181 ms

system.theme.css

system.theme.css

195 ms

date.css

date.css

211 ms

datepicker.1.7.css

datepicker.1.7.css

238 ms

date_repeat_field.css

date_repeat_field.css

359 ms

node.css

node.css

373 ms

search.css

search.css

395 ms

shadowbox.css

shadowbox.css

393 ms

base.css

base.css

478 ms

1x07_reset.css

1x07_reset.css

416 ms

1x07_2015.css

1x07_2015.css

567 ms

refinement.css

refinement.css

562 ms

guide.css

guide.css

584 ms

coreupdate.css

coreupdate.css

597 ms

topper.css

topper.css

593 ms

1x07_2015_promobox.css

1x07_2015_promobox.css

655 ms

jquery.fancybox.css

jquery.fancybox.css

747 ms

jquery.ui.core.css

jquery.ui.core.css

752 ms

jquery.ui.theme.css

jquery.ui.theme.css

766 ms

overlay-parent.css

overlay-parent.css

775 ms

jquery.min.js

jquery.min.js

911 ms

jquery.once.js

jquery.once.js

831 ms

drupal.js

drupal.js

926 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

928 ms

jquery.ba-bbq.js

jquery.ba-bbq.js

942 ms

overlay-parent.js

overlay-parent.js

959 ms

fr_qO4EtAhqyF0KTat3VnHVGnM31MHvE09qd3p5-1fI97s.js

fr_qO4EtAhqyF0KTat3VnHVGnM31MHvE09qd3p5-1fI97s.js

1010 ms

js

js

25 ms

googleanalytics.js

googleanalytics.js

1087 ms

toppers_tracking.js

toppers_tracking.js

1106 ms

autocomplete.js

autocomplete.js

1112 ms

googleads_home_fr.js

googleads_home_fr.js

1150 ms

script.js

script.js

1169 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

1199 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

1280 ms

jquery.ba-bbq.js

jquery.ba-bbq.js

1129 ms

tracking.js

tracking.js

1153 ms

jquery.cookie.js

jquery.cookie.js

1177 ms

shadowbox.js

shadowbox.js

1304 ms

footer.js

footer.js

1167 ms

xgemius.js

xgemius.js

451 ms

dc.js

dc.js

29 ms

__utm.gif

__utm.gif

12 ms

ga-audiences

ga-audiences

52 ms

gpt.js

gpt.js

25 ms

rta.js

rta.js

48 ms

pubads_impl_82.js

pubads_impl_82.js

6 ms

container.html

container.html

9 ms

fpdata.js

fpdata.js

96 ms

1307.be.png

1307.be.png

180 ms

135x100-bis.jpg

135x100-bis.jpg

194 ms

topper-135x100.jpg

topper-135x100.jpg

195 ms

proxifuel.55840be78dc1b3af458b4567.jpg

proxifuel.55840be78dc1b3af458b4567.jpg

194 ms

1307_universal_topper.png

1307_universal_topper.png

195 ms

accessible1307_0.png

accessible1307_0.png

297 ms

facebook_button.png

facebook_button.png

363 ms

close.png

close.png

375 ms

ads

ads

96 ms

search_arrow.gif

search_arrow.gif

329 ms

usefull_image.png

usefull_image.png

337 ms

bg_toppers.gif

bg_toppers.gif

339 ms

topper_cta_arrow.gif

topper_cta_arrow.gif

425 ms

searchbar2014.png

searchbar2014.png

475 ms

ft_bg.png

ft_bg.png

484 ms

bg_superfooter.png

bg_superfooter.png

500 ms

arr_6x8_21679e.png

arr_6x8_21679e.png

495 ms

skynet_logo.png

skynet_logo.png

511 ms

ico_info2.png

ico_info2.png

573 ms

1-iphone6s-1603-300x250-fr.jpg

1-iphone6s-1603-300x250-fr.jpg

32 ms

sbhK2lTE.js

sbhK2lTE.js

15 ms

modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js

modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js

24 ms

osd.js

osd.js

7 ms

lsget.html

lsget.html

238 ms

cTrvNaRi.html

cTrvNaRi.html

13 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

31 ms

index.html

index.html

69 ms

easeljs.min.js

easeljs.min.js

44 ms

TweenMax.min.js

TweenMax.min.js

57 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

36 ms

bg.png

bg.png

21 ms

line.png

line.png

6 ms

eyebrow-left.png

eyebrow-left.png

10 ms

eyebrow-right.png

eyebrow-right.png

11 ms

proximuslogo.png

proximuslogo.png

13 ms

button.png

button.png

16 ms

redpatch.png

redpatch.png

12 ms

pack.png

pack.png

14 ms

price.png

price.png

12 ms

months.png

months.png

13 ms

whitepatch.png

whitepatch.png

15 ms

title.png

title.png

15 ms

pupil-left.png

pupil-left.png

17 ms

pupil-right.png

pupil-right.png

17 ms

rexdot.js

rexdot.js

91 ms

__utm.gif

__utm.gif

16 ms

Accessibility Review

1407.be accessibility score

94

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

1407.be best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

1407.be 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

    DE

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

1407.be

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