Tools & Wizards About Us
stanley.hu screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

stanley.hu

Tolajt, Tolajts szekrny, Gardrbszekrny, Beptett szekrny, Stanley tkr tolajt, Gardrb

Page Load Speed

4.2 sec in total

First Response

167 ms

Resources Loaded

3.8 sec

Page Rendered

151 ms

stanley.hu screenshot

About Website

Visit stanley.hu now to see the best up-to-date Stanley content for Hungary and also check out these interesting facts you probably never knew about stanley.hu

Tolajt, Tolajts szekrny, Gardrbszekrny, Beptett szekrny, Gardrb, Stanley tolajts gardrbszekrny, Beptett szekrny mretre gyrtva, Tolajts szekrny egyedi mretre, Tkrajts szekrny, Tkr tolajt, Tkrajts gardr...

Visit stanley.hu

Key Findings

We analyzed Stanley.hu page load time and found that the first response time was 167 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

stanley.hu performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

frontpage.html

167 ms

ga.js

7 ms

css.css

357 ms

swffix_modified.js

652 ms

AC_RunActiveContent.js

700 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 64% of them (7 requests) were addressed to the original Stanley.hu, 18% (2 requests) were made to Google-analytics.com and 9% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Stanley.hu.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.7 kB (15%)

Content Size

265.0 kB

After Optimization

224.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Stanley.hu main page is 265.0 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. Only 10% of websites need less resources to load. Images take 245.2 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 1.6 kB

  • Original 2.6 kB
  • After minification 2.6 kB
  • After compression 1.0 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 1.6 kB or 61% of the original size.

Image Optimization

-16%

Potential reduce by 39.1 kB

  • Original 245.2 kB
  • After minification 206.2 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. Obviously, Stanley needs image optimization as it can save up to 39.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • Images
  • JavaScript

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stanley. According to our analytics all requests are already optimized.

Network Requests Diagram

frontpage.html

frontpage.html

167 ms

ga.js

ga.js

7 ms

css.css

css.css

357 ms

swffix_modified.js

swffix_modified.js

652 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

700 ms

__utm.gif

__utm.gif

22 ms

collect

collect

68 ms

ga-audiences

ga-audiences

33 ms

bg_right.jpg

bg_right.jpg

351 ms

index_01.jpg

index_01.jpg

628 ms

index_02.jpg

index_02.jpg

2221 ms

Accessibility Review

stanley.hu accessibility score

93

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

SEO Factors

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

    HU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1250

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stanley.hu can be misinterpreted by Google and other search engines. Our service has detected that Hungarian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stanley.hu main page’s claimed encoding is windows-1250. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

stanley.hu

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