Tools & Wizards About Us
funteq.com screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

funteq.com

ファンテック スピーカー修理・スピーカーエッジ交換・オーディオパーツ販売

Page Load Speed

3.2 sec in total

First Response

540 ms

Resources Loaded

2.5 sec

Page Rendered

164 ms

funteq.com screenshot

About Website

Click here to check amazing Funteq content for Japan. Otherwise, check out these important facts you probably never knew about funteq.com

ファンテック・スピーカー修理・スピーカーエッジ・各種オーディオパーツ販売・北海道

Visit funteq.com

Key Findings

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

Performance Metrics

funteq.com performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.162

72/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

funteq.com

540 ms

nvg.htm

181 ms

menu.htm

469 ms

home.htm

662 ms

FUNTEQ10.gif

205 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 6.5 kB (75%)

Content Size

8.7 kB

After Optimization

2.2 kB

  • HTML
  • CSS

In fact, the total size of Funteq.com main page is 8.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. CSS take 6.7 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 1.2 kB

  • Original 1.9 kB
  • After minification 1.5 kB
  • After compression 711 B

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 436 B, which is 23% 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 1.2 kB or 63% of the original size.

CSS Optimization

-78%

Potential reduce by 5.3 kB

  • Original 6.7 kB
  • After minification 5.2 kB
  • After compression 1.5 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. Funteq.com needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

  • AJAX
  • Images
  • CSS

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

Network Requests Diagram

funteq.com

funteq.com

540 ms

nvg.htm

nvg.htm

181 ms

menu.htm

menu.htm

469 ms

home.htm

home.htm

662 ms

FUNTEQ10.gif

FUNTEQ10.gif

205 ms

calendar.css

calendar.css

231 ms

style.css

style.css

292 ms

embk.gif

embk.gif

528 ms

reedge_img02.gif

reedge_img02.gif

1266 ms

contact.gif

contact.gif

174 ms

top_kit.gif

top_kit.gif

163 ms

top_heil.gif

top_heil.gif

495 ms

top_dia.gif

top_dia.gif

495 ms

top_parts.gif

top_parts.gif

612 ms

Count.cgi

Count.cgi

413 ms

Accessibility Review

funteq.com accessibility score

64

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.

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

funteq.com SEO score

67

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

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

funteq.com

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