Tools & Wizards About Us
glp.eu screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

glp.eu

GLP · Intellectual Property Office · Your European IP Partner

Page Load Speed

3.2 sec in total

First Response

324 ms

Resources Loaded

2.5 sec

Page Rendered

365 ms

glp.eu screenshot

About Website

Visit glp.eu now to see the best up-to-date GLP content for Italy and also check out these interesting facts you probably never knew about glp.eu

GLP: Intellectual property. Patents, trademarks and legal assistance.

Visit glp.eu

Key Findings

We analyzed Glp.eu page load time and found that the first response time was 324 ms and then it took 2.8 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

glp.eu performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

glp.eu

324 ms

161 ms

vcards.css

111 ms

pace.min.js

218 ms

bootstrap.min.css

417 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that all of those requests were addressed to Glp.eu and no external sources were called. The less responsive or slowest element that took the longest time to load (946 ms) belongs to the original domain Glp.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 155.7 kB (26%)

Content Size

607.2 kB

After Optimization

451.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Glp.eu main page is 607.2 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. 30% of websites need less resources to load. Images take 270.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 43.8 kB

  • Original 51.9 kB
  • After minification 43.7 kB
  • After compression 8.1 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 8.2 kB, which is 16% 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 43.8 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 12.2 kB

  • Original 270.7 kB
  • After minification 258.5 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. GLP images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 96.1 kB

  • Original 250.3 kB
  • After minification 247.7 kB
  • After compression 154.1 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 96.1 kB or 38% of the original size.

CSS Optimization

-10%

Potential reduce by 3.6 kB

  • Original 34.3 kB
  • After minification 34.3 kB
  • After compression 30.7 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. Glp.eu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (38%)

Requests Now

32

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

glp.eu

glp.eu

324 ms

161 ms

vcards.css

vcards.css

111 ms

pace.min.js

pace.min.js

218 ms

bootstrap.min.css

bootstrap.min.css

417 ms

main.css

main.css

311 ms

stylesheet.min.css

stylesheet.min.css

325 ms

settings.css

settings.css

335 ms

jquery.min.js

jquery.min.js

556 ms

jquery.bootstrap.min.js

jquery.bootstrap.min.js

341 ms

jquery.lazy.min.js

jquery.lazy.min.js

414 ms

jquery.scrollmagic.min.js

jquery.scrollmagic.min.js

655 ms

text_en.js

text_en.js

512 ms

main.js

main.js

513 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

728 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

625 ms

logo-glp-border.svg

logo-glp-border.svg

333 ms

glp-awards.png

glp-awards.png

686 ms

weloveip.jpg

weloveip.jpg

869 ms

handseed.png

handseed.png

659 ms

linkedin-logo.png

linkedin-logo.png

535 ms

timer.png

timer.png

374 ms

bgwelcome.svg

bgwelcome.svg

375 ms

sprite-rombo.svgz

sprite-rombo.svgz

600 ms

socialsprite.png

socialsprite.png

399 ms

wechat-icon.png

wechat-icon.png

556 ms

gidole-regular-webfont.woff

gidole-regular-webfont.woff

468 ms

crayon-crumble-webfont.woff

crayon-crumble-webfont.woff

946 ms

pier-webfont.woff

pier-webfont.woff

484 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

642 ms

346 ms

revicons.woff

revicons.woff

291 ms

team-thumb.jpg

team-thumb.jpg

217 ms

bimbo2-thumb.jpg

bimbo2-thumb.jpg

110 ms

Accessibility Review

glp.eu accessibility score

74

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

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

glp.eu best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

glp.eu SEO score

90

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

glp.eu

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