Tools & Wizards About Us

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

foreyever.com

Online Sunglasses for Women, Men and Kids | Foreyever® - Foreyever®

Page Load Speed

10.4 sec in total

First Response

2 sec

Resources Loaded

7.5 sec

Page Rendered

907 ms

About Website

Click here to check amazing Foreyever content for Italy. Otherwise, check out these important facts you probably never knew about foreyever.com

Foreyever® is an Italian brand of sunglasses. Visit our Online Store and discover our models for women, men and kids.

Visit foreyever.com

Key Findings

We analyzed Foreyever.com page load time and found that the first response time was 2 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

foreyever.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.415

23/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

1959 ms

global.css

266 ms

highdpi.css

298 ms

responsive-tables.css

300 ms

uniform.default.css

301 ms

Our browser made a total of 229 requests to load all elements on the main page. We found that 93% of them (213 requests) were addressed to the original Foreyever.com, 2% (4 requests) were made to Google-analytics.com and 1% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Foreyever.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 309.4 kB (14%)

Content Size

2.3 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foreyever.com main page is 2.3 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 246.9 kB

  • Original 267.3 kB
  • After minification 193.9 kB
  • After compression 20.4 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 73.4 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 246.9 kB or 92% of the original size.

Image Optimization

-1%

Potential reduce by 8.6 kB

  • Original 1.5 MB
  • After minification 1.5 MB

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. Foreyever images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 28.7 kB

  • Original 362.4 kB
  • After minification 361.5 kB
  • After compression 333.7 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.

CSS Optimization

-17%

Potential reduce by 25.3 kB

  • Original 147.9 kB
  • After minification 146.9 kB
  • After compression 122.6 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. Foreyever.com needs all CSS files to be minified and compressed as it can save up to 25.3 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 139 (63%)

Requests Now

222

After Optimization

83

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

foreyever.com accessibility score

54

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.

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

Form elements do not have associated labels

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

foreyever.com best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

foreyever.com SEO score

83

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foreyever.com 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 Foreyever.com 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

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