Tools & Wizards About Us
i-part.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

i-part.com

i-Part愛情公寓 | 提供聊天室約會聯誼的交友網站

Page Load Speed

4.7 sec in total

First Response

413 ms

Resources Loaded

4.2 sec

Page Rendered

150 ms

i-part.com screenshot

About Website

Click here to check amazing I Part content. Otherwise, check out these important facts you probably never knew about i-part.com

提供聊天室傳情聊天、網路交友、徵友約會聯誼等服務，是全國最大、最受女生歡迎的線上交友網站，超過500萬的單身男女入住愛情公寓，想要找談心好友、興趣同好、男女朋友、結婚對象…，通通都在這裡，快來寓約您的愛情、寓見您的幸福。

Visit i-part.com

Key Findings

We analyzed I-part.com page load time and found that the first response time was 413 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

i-part.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.347

32/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

i-part.com

413 ms

www.i-part.com.tw

913 ms

indexStyle.css

403 ms

ipart.css

773 ms

ipart_header_footer.css

399 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original I-part.com, 31% (26 requests) were made to Van.ipimg.com and 18% (15 requests) were made to I-part.com.tw. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Van.ipimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.5 kB (21%)

Content Size

574.2 kB

After Optimization

455.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I-part.com main page is 574.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. 35% of websites need less resources to load. Images take 325.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 68.7 kB

  • Original 82.9 kB
  • After minification 69.1 kB
  • After compression 14.2 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 13.8 kB, which is 17% 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 68.7 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 25.2 kB

  • Original 325.9 kB
  • After minification 300.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. I Part images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 19.3 kB

  • Original 146.3 kB
  • After minification 135.0 kB
  • After compression 127.0 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 19.3 kB or 13% of the original size.

CSS Optimization

-27%

Potential reduce by 5.2 kB

  • Original 19.1 kB
  • After minification 19.1 kB
  • After compression 13.9 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. I-part.com needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (43%)

Requests Now

83

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i-part.com

i-part.com

413 ms

www.i-part.com.tw

www.i-part.com.tw

913 ms

indexStyle.css

indexStyle.css

403 ms

ipart.css

ipart.css

773 ms

ipart_header_footer.css

ipart_header_footer.css

399 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

1163 ms

index.js

index.js

598 ms

indexV2.js

indexV2.js

758 ms

fbds.js

fbds.js

799 ms

ie_pinning_notification.js

ie_pinning_notification.js

791 ms

search_city.v2.js

search_city.v2.js

1394 ms

index_zoneSTC.js

index_zoneSTC.js

1142 ms

jquery.blockUI.js

jquery.blockUI.js

1154 ms

recognize_msgbox.js

recognize_msgbox.js

988 ms

fbevents.js

fbevents.js

172 ms

ytc.js

ytc.js

167 ms

headerBg.gif

headerBg.gif

217 ms

ipartLogo.png

ipartLogo.png

221 ms

sw_btn.png

sw_btn.png

225 ms

photo_1719703758.jpg

photo_1719703758.jpg

214 ms

30109_17211112351.jpg

30109_17211112351.jpg

75 ms

photo_1721622064.jpg

photo_1721622064.jpg

211 ms

photo_1659047090.jpg

photo_1659047090.jpg

585 ms

photo_1722608843.jpg

photo_1722608843.jpg

621 ms

photo_1722767325.jpg

photo_1722767325.jpg

218 ms

photo_1718719971.jpg

photo_1718719971.jpg

568 ms

photo_1647448885.jpg

photo_1647448885.jpg

237 ms

photo_1462664077.jpg

photo_1462664077.jpg

230 ms

photo_1675698743.jpg

photo_1675698743.jpg

235 ms

photo_1722114711.jpg

photo_1722114711.jpg

236 ms

photo_1696077831.jpg

photo_1696077831.jpg

249 ms

photo_1722472357.jpg

photo_1722472357.jpg

247 ms

photo_1472061402.jpg

photo_1472061402.jpg

243 ms

online.gif

online.gif

402 ms

icon_free.gif

icon_free.gif

212 ms

icon_bulletin_1.gif

icon_bulletin_1.gif

220 ms

footer_ipartLogo.png

footer_ipartLogo.png

229 ms

footer_ios2.png

footer_ios2.png

229 ms

footer_android2.png

footer_android2.png

220 ms

footer_fb_icon.png

footer_fb_icon.png

226 ms

footer_fb.png

footer_fb.png

225 ms

arraw20.gif

arraw20.gif

227 ms

photo_1722645455s.jpg

photo_1722645455s.jpg

219 ms

online.gif

online.gif

244 ms

g.gif

g.gif

219 ms

photo_1711422612s.jpg

photo_1711422612s.jpg

893 ms

photo_1721780382s.jpg

photo_1721780382s.jpg

233 ms

arraw20.gif

arraw20.gif

230 ms

in_yes.png

in_yes.png

229 ms

in_no.png

in_no.png

232 ms

b.gif

b.gif

847 ms

g.gif

g.gif

231 ms

icon_c0.gif

icon_c0.gif

897 ms

icon_c2.gif

icon_c2.gif

240 ms

saylove_1324620670s.jpg

saylove_1324620670s.jpg

888 ms

saylove_1250734202s.jpg

saylove_1250734202s.jpg

905 ms

space.gif

space.gif

246 ms

button_close.gif

button_close.gif

249 ms

online_s.gif

online_s.gif

912 ms

photo_1722686714c.jpg

photo_1722686714c.jpg

1483 ms

photo_1722402894c.jpg

photo_1722402894c.jpg

1598 ms

photo_1721886862c.jpg

photo_1721886862c.jpg

1578 ms

photo_1721832164c.jpg

photo_1721832164c.jpg

1563 ms

photo_1721903101c.jpg

photo_1721903101c.jpg

1535 ms

fbds.js

fbds.js

163 ms

428555.json

428555.json

63 ms

search_city.v2.1.zh_tw.js

search_city.v2.1.zh_tw.js

834 ms

SubFrameTitleBg1.png

SubFrameTitleBg1.png

42 ms

SubFrameTitleBg2.png

SubFrameTitleBg2.png

39 ms

photo_1633075522.jpg

photo_1633075522.jpg

730 ms

30115_17225073641.jpg

30115_17225073641.jpg

6 ms

picBg.gif

picBg.gif

5 ms

broadcast_bg.gif

broadcast_bg.gif

20 ms

SubFrameBg.jpg

SubFrameBg.jpg

20 ms

photobg06.gif

photobg06.gif

19 ms

photobg07.gif

photobg07.gif

20 ms

ga.js

ga.js

11 ms

like.php

like.php

112 ms

__utm.gif

__utm.gif

13 ms

__utm.gif

__utm.gif

6 ms

KKhk6eugt1M.js

KKhk6eugt1M.js

28 ms

FEppCFCt76d.png

FEppCFCt76d.png

27 ms

rec.js

rec.js

20 ms

jquery.min.js

jquery.min.js

29 ms

ls.html

ls.html

432 ms

Accessibility Review

i-part.com accessibility score

45

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-part.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 I-part.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

i-part.com

Open Graph data is detected on the main page of I Part. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: