Ufeff.com Site Title

生态增养殖-水产品深加工-东营菲芬海洋科技有限公司

Ufeff.com Meta Description

东营菲芬海洋科技有限公司成立于2021年07月23日，注册地位于山东省东营市河口区仙河镇中心渔港管理站向西500米路北，法定代表人为孙学城。经营范围包括一般项目：海洋生物活性物质提取、纯化、合成技术研发；海洋工程关键配套系统开发；海洋工程装备研发；自然科学研究和试验发展；工程和技术研究和试验发展；技术服务、技术开发、技术咨询、技术交流、技术转让、技术推广；科普宣传服务；海洋服务；渔业机械服务；生态恢复及生态保护服务；生态保护区管理服务；工业设计服务；水生植物种植；农林牧渔业废弃物综合利用；海洋环境监测与探测装备销售；海水养殖和海洋生物资源利用装备销售；水产品零售；水产品批发；计算机软硬件及辅助设备批发；水产品收购。（除依法须经批准的项目外，凭营业执照依法自主开展经营活动）

Ufeff.com Test Results

Ufeff.com Mobile Performance: 82/100
Quick overview:
Time to Interactive
4.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
120 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
2.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Network Round Trip Times
400 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Diagnostics
Collection of useful page vitals.
Metrics
Collects all available metrics.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Script Treemap Data
Used for treemap app
Server Backend Latencies
370 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Network Requests
Lists the network requests that were made during page load.
Final Screenshot
The last screenshot captured of the pageload.

1374873702852


Ufeff.com Mobile SEO: 89/100
Quick overview:
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
64% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Ufeff.com Mobile Best Practices: 64/100
Quick overview:
Trust and Safety
Does not use HTTPS
3 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Ufeff.com Mobile PWA: 38/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: No manifest was fetched.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Ufeff.com Mobile Accessibility: 40/100
Quick overview:
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Definition list items are not wrapped in `<dl>` elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Navigation
These are opportunities to improve keyboard navigation in your application.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
Similar tests
www.ufeff.com
www.ufeff.net
www.ufeff.org
www.ufeff.info
www.ufeff.biz
www.ufeff.us
www.ufeff.mobi
www.feff.com
www.ufeff.com
www.yfeff.com
www.uyfeff.com
www.yufeff.com
www.hfeff.com
www.uhfeff.com
www.hufeff.com
www.jfeff.com
www.ujfeff.com
www.jufeff.com
www.ifeff.com
www.uifeff.com
www.iufeff.com
www.ueff.com
www.uceff.com
www.ufceff.com
www.ucfeff.com
www.udeff.com
www.ufdeff.com
www.udfeff.com
www.ureff.com
www.ufreff.com
www.urfeff.com
www.uteff.com
www.ufteff.com
www.utfeff.com
www.ugeff.com
www.ufgeff.com
www.ugfeff.com
www.uveff.com
www.ufveff.com
www.uvfeff.com
www.ufff.com
www.ufwff.com
www.ufewff.com
www.ufweff.com
www.ufsff.com
www.ufesff.com
www.ufseff.com
www.ufdff.com
www.ufedff.com
www.ufrff.com
www.uferff.com
www.ufef.com
www.ufecf.com
www.ufefcf.com
www.ufecff.com
www.ufedf.com
www.ufefdf.com
www.uferf.com
www.ufefrf.com
www.ufetf.com
www.ufeftf.com
www.ufetff.com
www.ufegf.com
www.ufefgf.com
www.ufegff.com
www.ufevf.com
www.ufefvf.com
www.ufevff.com
www.ufefc.com
www.ufeffc.com
www.ufefd.com
www.ufeffd.com
www.ufefr.com
www.ufeffr.com
www.ufeft.com
www.ufefft.com
www.ufefg.com
www.ufeffg.com
www.ufefv.com
www.ufeffv.com
www.ufeff.con
Last Tested: